Inventory (UXPROD-785)

[UXPROD-2703] Inventory. Result list. Refined display rules MCL. Adding publication date Created: 30/Sep/20  Updated: 05/Feb/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: Trillium (R1 2025)
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Christine Schultz-Richert
Resolution: Unresolved Votes: 0
Labels: LC-priority3, at-risk, loc, metadatamanagement, po-mvp, round_iv, search_result, short_term_solution
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Skärmavbild 2021-12-13 kl. 3.44.49 em.png    
Issue links:
Blocks
is blocked by MSEARCH-60 Sorting results - publication date Closed
Defines
is defined by MODINVSTOR-723 Add sortable publication year field t... Closed
is defined by MODINVSTOR-724 Populate publication year field based... Closed
is defined by UIIN-1657 publisher sort fails with an Okapi error Closed
is defined by MSEARCH-203 Split Publishers column into two sepa... Draft
is defined by UIDATIMP-752 Update MARC-Instance map to account f... Blocked
is defined by UIIN-1876 Result list. Add publication year. Blocked
Relates
relates to UX-449 UX: Sort by values for updated invent... Open
Requires
requires MODINVSTOR-1104 Pub dates that start with hyphen are ... Open
Epic Link: Inventory
Front End Estimate: Small < 3 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: Large < 10 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Spitfire
Kiwi Planning Points (DO NOT CHANGE): 2
PO Rank: 110
Rank: Chalmers (Impl Aut 2019): R3
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R4
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

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: MODINVSTOR-723 Closed
  • Populated publicationPeriod element from data in publication year field: MODINVSTOR-724 Closed
  • Need to split "Publisher" column into Publisher and dates, add new column for Publication date:
  • 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 ( UXPROD-491 Analysis Complete ), if at all possible, is in our best interest.
Charlotte Whitt: See more comments added 2/23/2020 in UXPROD-491 Analysis Complete .

  • - - - - - - - - - - - - - 

This feature is split out of UXPROD-1634 Closed - 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:

  1. UXPROD-1634 Closed (index title/title)
  2. UXPROD-2667 Open (sort on contributor, when more than one contributor is listed)
  3. UXPROD-2668 Open (Adding instance HRID)
  4. UXPROD-2669 Open (Adding resource type)
  5. UXPROD-2670 Draft (Adding format)
  6. UXPROD-2671 Open (Adding edition)
  7. UXPROD-2703 (Adding publication date)

Documentation:

  1. 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
  2. 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
  3. UX mock up

 



 Comments   
Comment by Jessica Janecki [ 12/Oct/20 ]

How will the date be abstracted? The 260/264 $c can contain a lot of text other than a single date. Also, not all records have a 260/264 but do have a publication date encoded elsewhere in the record.

Comment by Charlotte Whitt [ 14/Oct/20 ]

Hi Jessica Janecki - 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

Comment by Marc Johnson [ 14/Oct/20 ]

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?

Comment by Charlotte Whitt [ 14/Oct/20 ]

Marc Johnson - 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'.

Comment by Charlotte Whitt [ 13/Feb/23 ]

Magda Zacharska I'll unblock this feature now the work on MODINVSTOR-723 Closed has been completed and a new property (data element) has bee implemented.

CC: Felix Hemme

Comment by Khalilah Gambrell [ 08/Sep/23 ]

Hey Christine Schultz-Richert is this still a LC3 feature?

Generated at Fri Feb 09 00:26:10 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.