Inventory. Result list. Refined display rules MCL. Adding publication date

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:

  • Populated publicationPeriod element from data in publication year field:

  • 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 (), 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:

  1. (index title/title)

  2. (sort on contributor, when more than one contributor is listed)

  3. (Adding instance HRID)

  4. (Adding resource type)

  5. (Adding format)

  6. (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

 

Priority

Fix versions

None

Development Team

Spitfire

Assignee

Christine Schultz-Richert

Solution Architect

Parent Field Value

None

Parent Status

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

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 AM
Edited

- 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

Reporter

PO Rank

110

Front End Estimate

Small < 3 days

Front End Estimator

Front-End Confidence factor

20%

Back End Estimate

Large < 10 days

Back End Estimator

Back-End Confidence factor

20%

Rank: FLO (MVP Sum 2020)

R1

Rank: 5Colleges (Full Jul 2021)

R1

Rank: Cornell (Full Sum 2021)

R5

Rank: Chalmers (Impl Aut 2019)

R3

Rank: GBV (MVP Sum 2020)

R4

Rank: hbz (TBD)

R1

Rank: Hungary (MVP End 2020)

R1

Rank: Grand Valley (Full Sum 2021)

R4

Rank: TAMU (MVP Jan 2021)

R1

Rank: Chicago (MVP Sum 2020)

R1

Rank: MO State (MVP June 2020)

R2

Rank: U of AL (MVP Oct 2020)

R1

Rank: Lehigh (MVP Summer 2020)

R1

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 30, 2020 at 3:18 PM
Updated September 6, 2024 at 9:05 AM
TestRail: Cases
TestRail: Runs