Metadata Record Export (UXPROD-652)

[UXPROD-141] Export Inventory Instances with underlying SRS records to MARC Bib Created: 18/Jan/18  Updated: 16/Sep/20  Resolved: 14/Mar/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2020
Parent: Metadata Record Export

Type: New Feature Priority: P1
Reporter: Cate Boerema (Inactive) Assignee: Magda Zacharska
Resolution: Done Votes: 0
Labels: Lehigh(round_ii+mvp), cap-mvp, export, inventory, metadatamanagement, po-mvp, q4-2019-at-risk, q4-2019-spillover, split
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-2315 Export Inventory Instances to other n... Closed
Defines
defines UXPROD-652 Metadata Record Export In Progress
is defined by MDEXP-1 SPIKE: Investigate the way to read la... Closed
is defined by MDEXP-2 Save binary MARC file in the designa... Closed
is defined by MDEXP-34 Export inventory instance record with... Closed
is defined by MDEXP-36 RecordLoaderService: retrieve MARC re... Closed
is defined by MDEXP-54 Implement the export flow Closed
is defined by MDEXP-69 Update a jobExecution entry in DB Closed
Relates
relates to UXPROD-977 Export Inventory Items to a delimited... Open
relates to UXPROD-1397 Generating a MARC bibliographic recor... Closed
relates to UXPROD-1577 Make Inventory Instance rely on SRS M... Closed
relates to UXPROD-142 Export Holdings from SRS MARC holdings Closed
relates to UXPROD-2224 Export Inventory Instances to MARCXML... Open
Epic Link: Metadata Record Export
Analysis Estimate: Large < 10 days
Analysis Estimator: Charlotte Whitt
Front-End Confidence factor: Low
Back End Estimate: XL < 15 days
Back End Estimator: Taras Spashchenko
Estimation Notes and Assumptions: Depends on number and types of formats to support.
Development Team: Concorde
PO Rank: 104
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
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: hbz (TBD): R2
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: Leipzig (Full TBD): R4
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R4

 Description   

Inventory instance records will need to be exported into the output format defined by the user needs. If the user requests MARC output format and the instance record has an associated MARC Bib record in SRS, then underlying SRS record will be exported.

The selection of the records to be exported bases on the list of the provided UUIDs

As discussed in Export use cases the most common formats are MARC and delimited files. This feature covers exporting inventory instance records in MARC21.

Note: Data manipulation (included fields, mappings) and combining instance data with holdings and items is a part of the Metadata Export Mapping Profile ( UXPROD-2153 Closed )



 Comments   
Comment by Hkaplanian [ 19/Feb/18 ]

For V1, this should be MARC21 or the format required by an external editor such as MARCedit

Comment by Cate Boerema (Inactive) [ 24/May/18 ]

From Ann-Marie Breaux (email May 24, 2018):

A question came up in yesterday’s batch loader meeting. I’m sending to you as the Inventory PO, but it has Discovery implications as well, so copying Harry and Cate, in case it should go to someone else too, and Lynn since it’s catalog-related.

We can’t assume that the MARC storage area in FOLIO will have all of a library’s titles in it. Some may be inventory instances without underlying MARC records. In some cases, those free-floating instances may be suppressed from discovery, but in other cases, the library may want to output those free-floating inventory records to discovery.

Discovery layers learn about the library’s local inventory via catalog exports, which are then loaded to discovery. Those basic exports tend to be MARC-formatted files, scheduled for output from the ILS on a regular basis, for updating the discovery layer. There’s also discovery integrations like real-time availability checking, which are powered by API rather than batch loads.

Have we sorted out how FOLIO catalog data will be formatted and exported to power the library’s discovery layer? Is that on someone’s radar? It may be part of the overall “export” portion of FOLIO, which does not have a PO yet. Or maybe integration with systems external to FOLIO.

In any event – I wanted to get this on someone’s radar besides mine!

Comment by Anya [ 29/Mar/19 ]

UA : item record is important to be able to export -but as written not needed

Comment by Magda Zacharska [ 13/Nov/19 ]

Example of Inventory Instance json format (from Bugfest environment)

{
  "id": "d73af411-b1b4-444c-a77a-547475f455d3",
  "hrid": "in01201671",
  "source": "chalmers_dump.2019-05-15_1312",
  "title": "A brief history of Chalmers by Jan Hult",
  "indexTitle": "brief history of Chalmers",
  "alternativeTitles": [
    {
      "alternativeTitleTypeId": "d7f2124f-fdaa-450b-9b37-2b1c183ca379",
      "alternativeTitle": "Chalmers History"
    }
  ],
  "editions": [
    "1st edition"
  ],
  "series": [
    "Great colleges of Sweden; v. 3"
  ],
  "identifiers": [
    {
      "value": "992-940155-5",
      "identifierTypeId": "8261054f-be78-422d-bd51-4ed9f33c3422"
    },
    {
      "value": "9929401555",
      "identifierTypeId": "5d164f4b-0b15-4e42-ae75-cfcf85318ad9"
    },
    {
      "value": "1122587",
      "identifierTypeId": "3187432f-9434-40a8-8782-35a111a1491e"
    },
    {
      "value": "2801039",
      "identifierTypeId": "925c7fb9-0b87-4e16-8713-7f4ea71d854b"
    }
  ],
  "contributors": [
    {
      "name": "Hult, Jan",
      "contributorTypeId": "6e09d47d-95e2-4d8a-831b-f777b8ef6d81",
      "contributorNameTypeId": "2b94c631-fca9-4892-a730-03ee529ffe2a",
      "primary": true
    }
  ],
  "subjects": [
    "Lucifer",
    "French fries"
  ],
  "classifications": [],
  "publication": [
    {
      "publisher": "Chalmers Public Relations and Press Office,",
      "place": "Göteborg :",
      "dateOfPublication": "1999"
    }
  ],
  "publicationFrequency": [],
  "publicationRange": [],
  "electronicAccess": [],
  "instanceTypeId": "a2c91e87-6bab-44d6-8adb-1fd02481fc4f",
  "instanceFormatIds": [],
  "physicalDescriptions": [
    "42 s. : ill. 30 cm"
  ],
  "languages": [
    "eng",
    "swe"
  ],
  "notes": [],
  "modeOfIssuanceId": "9d18a02f-5897-4c31-9106-c9abb5c7ae8b",
  "catalogedDate": "2019-06-03",
  "discoverySuppress": false,
  "statisticalCodeIds": [],
  "statusId": "2a340d34-6b70-443a-bb1b-1b8d1c65d862",
  "metadata": {
    "createdDate": "2019-06-20T19:41:49.890+0000",
    "createdByUserId": "cf0dc59d-38ef-40b7-a233-f4e613286b45",
    "updatedDate": "2019-06-20T19:41:49.890+0000",
    "updatedByUserId": "cf0dc59d-38ef-40b7-a233-f4e613286b45"
  },
  "holdingsRecords2": [],
  "natureOfContentTermIds": []
}
Comment by Jennifer Eustis [ 14/Nov/19 ]

For the question, I would agree that MARC21 should be first. Then delimited and MARC json. Right now I can't think of other formats to export.

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