Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-138

Locally-stored metadata records for eResources in Inventory



    • Medium < 5 days
    • Medium < 5 days
    • Low
    • Medium < 5 days
    • Prokopovych
    • R1
    • R5
    • R1
    • R4
    • R2
    • R2
    • R4
    • R4
    • R5


      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 (instance), UXPROD-123(holdings), UXPROD-124(items)) then representation of eResources in Inventory is fully implemented.

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

      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.

      TestRail: Results


          Issue Links



                charlotte Charlotte Whitt
                cboerema Cate Boerema
                Charlotte Whitt Charlotte Whitt
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                0 Vote for this issue
                4 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases