Inventory. Result list. Refined display rules MCL. Adding publication date
Description
Priority
Fix versions
Development Team
Assignee
Solution Architect
Parent
Parent Field Value
Parent Status
Attachments
is blocked by
is defined by
relates to
Checklist
hideTestRail: Results
Activity
Khalilah Gambrell September 8, 2023 at 2:25 PM
Hey is this still a LC3 feature?
Charlotte Whitt February 13, 2023 at 10:18 AM
I'll unblock this feature now the work on MODINVSTOR-723 has been completed and a new property (data element) has bee implemented.
CC:
Charlotte Whitt October 14, 2020 at 11:42 AMEdited
- we want to strip the text and only use the numeric values in the date, e.g. 1960 if 'copyright 1960'; one exception though we need to preserve the dash if we have a date range, e.g. 1960-1970, if 'copyright 1960-1970'.
Marc Johnson October 14, 2020 at 11:39 AM
I want the search results to display the publication date (YYYY, or date range YYYY-YYYY) to help better distinct identical titles.
As I understand it, publication dates are not always structured in this format. Are we expecting the system to interpret the publication dates entered and convert them to either a year or a range of years?
Charlotte Whitt October 14, 2020 at 9:51 AM
Hi - the publication date data is fetched from the data element 'Publication date in the instance record'. The display in the column is intended to be numeric (so all text to be skipped), and only yyyy or a date range yyyy-yyyy.
What data to be populated in the publication date data element is defined when spec of the wanted data migration defined by the tenant, or by using the default MARC Bib to Instance mapping - https://github.com/folio-org/mod-source-record-manager/blob/master/mod-source-record-manager-server/src/main/resources/rules/rules.json
Overview: The ability to view and sort by publication date in Inventory results helps librarians differentiate between titles.
In scope:
Creating sortable publication date field
Adding publication date column to Inventory results list (and split from Publishers column)
Update mapping to new sortable publication date field
Out of scope:
Future need: customizable results lists (tenant level and user level)
Proposed solution/stories:
Create new property with a sortable publication date - created publicationPeriod with start and end date properties:
Populated publicationPeriod element from data in publication year field:
Need to split "Publisher" column into Publisher and dates, add new column for Publication date:
(split column)
https://folio-org.atlassian.net/browse/UIIN-1876 (add publication year column)
Data import? Mapping changes?: UIDATIMP-752{*}
*
Previous description related to splitting results list additions into separate features----
Laura Daniels:
MM SMEs have expressed a desire, that is, to focus on the longer-term goals rather than interim goals if they can't be built on directly. The lack, for instance, of call number in the search results display of the holdings segment, would not be addressed by the improvements in the JIRA features listed below. So I agree with you, @charlotte, that putting resources toward the hierarchical display instead (), if at all possible, is in our best interest.
: See more comments added 2/23/2020 in .
- - - - - - - - - - - - -
This feature is split out of UXPROD-1634 - the library ranking is kept from the original feature, which previously included all relevant refinements of the result list for the MVP.
The cap.plan team has asked for getting the different improvements split into their own feature:
(index title/title)
(sort on contributor, when more than one contributor is listed)
(Adding instance HRID)
(Adding resource type)
(Adding format)
(Adding edition)
UXPROD-2703 (Adding publication date)
Documentation:
Slide deck reviewed by MM-SIG 10/1/2020 and 10/8/2020 - https://docs.google.com/presentation/d/1kDumWwhNfP7Mq9hZ5q4O1cnbg_BY4ILgKbjBWOO4Xso/edit#slide=id.p
Survey send out on the #metadata-management channel 10/7/2020 - https://docs.google.com/presentation/d/13Dt-Tkr_nzgU2Oxb044J4d3RSxxk4R-0lq-AlKXIItg/edit#slide=id.g9998cb799b_2_0
UX mock up