Inventory (UXPROD-785)

[UXPROD-138] Locally-stored metadata records for eResources in Inventory Created: 18/Jan/18  Updated: 16/Sep/20  Resolved: 14/Sep/18

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2018
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Charlotte Whitt
Resolution: Done Votes: 0
Labels: crossrmapps, inventory, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-1080 Locally-stored metadata records for e... Closed
Relates
relates to UIIN-229 Instance Record. Accordion Electronic... Closed
relates to UXPROD-151 Ebook packages - relationship to indi... Draft
relates to UXPROD-492 Analyse and implement container objec... In Refinement
relates to FOLIO-1273 Define and describe the architecture ... Open
relates to FOLIO-1331 Define and describe the architecture ... Open
relates to UXPROD-127 A process is needed to periodically r... Draft
Epic Link: Inventory
Analysis Estimate: Medium < 5 days
Analysis Estimator: Charlotte Whitt
Front End Estimate: Medium < 5 days
Front End Estimator: Niels Erik Nielsen
Front-End Confidence factor: Low
Back End Estimate: Medium < 5 days
Back End Estimator: Niels Erik Nielsen
Development Team: Prokopovych
Rank: BNCF (MVP Feb 2020): R1
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R2
Rank: Lehigh (MVP Summer 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R5

 Description   

The metadata elements are included in: https://docs.google.com/spreadsheets/d/1RCZyXUA5rK47wZqfFPbiRM0xnw8WnMCcmlttT7B3VlI/edit#gid=952741439

When the suite of jira's implementing all the new elements and reorder data ( UXPROD-122 Closed (instance), UXPROD-123 Closed (holdings), UXPROD-124 Closed (items)) then representation of eResources in Inventory is fully implemented.

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

NOTES:
Locally-stored metadata records for eResources
Source: https://discuss.folio.org/t/locally-stored-metadata-records-for-eresources/1280/9

Email from Kristin Martin (6/7/2018)
Chicago’s local gap analysis spreadsheet: https://docs.google.com/spreadsheets/d/1qedy8xGmi_3rv8Krv0FaDnSEd-e7PiKeOabA_YqPZO8/edit#gid=1789724001

The groups gap analysis spreadsheet: https://docs.google.com/spreadsheets/d/1JnvLq-pQ861pNnW_AEn0xsSujr9yTuM8MOHSWJ_XSZA/edit#gid=2081002066

We are going on the assumption that print materials will have instance, holdings, and item records in Inventory, but electronic materials will only have instance and holdings records for the University of Chicago.

Summary of items, which we will indicate in the spreadsheet:

  • URL
  • Link text
  • Public Note
  • Materials Specified
  • Statistical code
  • Location
  • Call number

The first four items can be derived from the 856 field. Statistical code would be a locally defined FOLIO field, but one that we find necessary because MARC does not always represent different format types accurately (e.g., streaming video is notoriously difficult to identify from MARC fields). Location and call number are needed for all holdings. These fields are all needed for discovery purposes.

There are a number of other data elements that exist in OLE’s e-holdings record that are ERM-related. These are noted Chicago’s local gap analysis spreadsheet and include things like coverage dates, perpetual access dates, platform information, simultaneous users, etc. How we want this type of data represented in FOLIO will be dependent on the outcome of the ERM subgroup. uChicago are comfortable with deferring the decision on what to do with these data elements, and whether inventory is the right place for them to be placed, so long as we can return to Inventory and make adjustments as needed. The relationship between Inventory and the FOLIO e-holdings app is still to be determined as well.



 Comments   
Comment by Charlotte Whitt [ 05/Apr/18 ]

As follow up on todays MM-SIG meeting (https://folio-org.atlassian.net/wiki/display/MM/2018-04-05+Metadata+Management+Meeting+Notes) we'll need further analyze of implementation of the package model (container model) suggested by VBar - https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=5854462 and drill down to the paragraph on ‘Package’

Comment by Charlotte Whitt [ 23/Aug/18 ]

The metadata elements are included in: https://docs.google.com/spreadsheets/d/1RCZyXUA5rK47wZqfFPbiRM0xnw8WnMCcmlttT7B3VlI/edit#gid=952741439

When the suite of jira's implementing all the new elements and reorder data ( UXPROD-122 Closed , UXPROD-123 Closed , UXPROD-124 Closed ) then eResources in Inventory is implemented.

Next step will be to load test data.

Comment by Charlotte Whitt [ 03/Sep/18 ]

Hi Cate Boerema At today's FOLIO Team Meet (9/3) is was decided to focus only on implementing UXPROD-122 Closed (update the Instance record with new elements - front end and back end), and postpone update of the Holdings ( UXPROD-123 Closed ) and Item record ( UXPROD-124 Closed ). This means that this feature also will be implemented when it comes to the Instance record, but the Holdings and item part will be postponed to Q4 2018. I'll add a new feature for this - UXPROD

Comment by Cate Boerema (Inactive) [ 11/Sep/18 ]

Thanks for creating that feature, Charlotte Whitt. For reporting, it's important that only the stories that comprise this feature are linked to it. Given that, I just removed the link to the holdings and item stories ( UIIN-236 Closed and UIIN-256 Closed )

Comment by Charlotte Whitt [ 11/Sep/18 ]

Thanks! Cate Boerema

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