MVP Sierra integration

[mikeapp]

Story

Sierra should be added as a metadata source in DCS. This work should be done in a feature branch.

Prerequisite: #2499

Acceptance

• [x] Add Sierra as an Authoritative Metadata Source in Management DB
  • [x] The Metadata Cloud name for this source should be sierra and the display name Sierra
• [x] Batch jobs that accept a metadata source should accept this new code
• [x] Metadata should be fetched from the MC endpoint for Sierra
  • [x] MC API URL is dependent on #2499
• [x] Review codebase for other string references to metadata sources that might need to be changed.
  • [x] Looks like a literal array is used in the data tables (refactor?)

[jpengst]

PR: https://github.com/yalelibrary/yul-dc-management/pull/1207

[mikeapp]

Comments on PR, also created #2514 for future work on the datatable. There are probably additional tickets needed for display of Sierra info on the Parent Object page.

[mikeapp]

"Review on Demo"

[MaggieZhaoYale]

Example of Sierra metadata cloud: https://metadata-api-uat.library.yale.edu/metadatacloud/api/sierra/bib/273496?mediaType=json or https://metadata-api-uat.library.yale.edu/metadatacloud/api/# version/sierra/bib/273496?mediaType=json

[sshetenhelm]

Testing on demo using 'create parent objects' batch process.

• Parent object created
• Metadata Cloud provides json via link
• No json in object

Received following error message:

Setup job failed to save: undefined method `siera_json=' for #<ParentObject:0x0000564241660df8> Did you mean? sierra_json= sierra_json sierra_json?

PS - Added 'law' as a set in Demo to keep track of objects

[jpengst]

Oh, whoops! Typo in siera_json :(

[jpengst]

Typo PR: https://github.com/yalelibrary/yul-dc-management/pull/1210

[jpengst]

Trying to test this on demo but Solr seems to be down. Received a 500 Solr error when trying to delete an object. Create Parent Batch Process also reports 500 Solr.

[jpengst]

Testing on demo. Batch fails for undefined method zero?

I think this is being thrown in the sierra_json method for itemID

[jpengst]

PR for itemID check: https://github.com/yalelibrary/yul-dc-management/pull/1217

[jpengst]

bug fix deployed to Demo

[sshetenhelm]

Sierra JSON present for parent created through batch process (no children so no SOLR)

Sierra JSON present for existing parent object attached to Sierra. MOSTLY Sierra metadata displays in Blacklight, HOWEVER under the 'identifiers' section, the Law bib of 273496 make a /10079/bibid handle that points to the Orbis bib of the same number (SEE: 273496 )

[jpengst]

I'm looking at this this morning and noticed this Sierra items Identifier section with the Orbis Record id and link is consistent with other objects Identifier section on the site. Should the Orbis Record number and link be something different?

[sshetenhelm]

If an object has Sierra as its data source:

• Front end should display "Morris Record" instead of Orbis record
• Created link should have prefix of https://morris.law.yale.edu/record=b (so full link would be ex. https://morris.law.yale.edu/record=b273496)

[jpengst]

PR:
https://github.com/yalelibrary/yul-dc-blacklight/pull/906

[jpengst]

Deployed to Demo

[sshetenhelm]

Yeeessss this is amazing! Looks great on Demo! THANK YOU!