testing alma XSLT

[yulgit1]

@flapka before your last day friday would like to make sure I good representative examples of mms IDs and their corresponding bibids, as well as how to index the 852, 541s. I assume we need to have like the following as in for the record: https://collections.britishart.yale.edu/catalog/orbis:12599233

Holdings:
Rare Books and Manuscripts
QL805.S78 C66 1802+ Oversize
Yale Center for British Art, Paul Mellon Fund
[Request]

[Request] = 
https://aeon.library.yale.edu/aeon.dll?Action=10&Form=20&Value=GenericRequestMonograph&Site=YCBA&CallNumber=QL805.S78 C66 1802+ Oversize&ItemTitle=Proposals for publishing, a comparative anatomical exposition of the structure of the human body, with that of a tyger and a common fowl : in thirty tables, two copper-plates to each table, 20 inches by 15 : forming six numbers, ten plates to each number / the whole executed by George Stubbs, author of "The anatomy of the horse."&ItemAuthor=Stubbs, George, 1724-1806&ItemDate=1802&Format=1 sheet ([2] pages) ; 29 x 18 cm&Location=bacrb&mfhdID=12720666&EADNumber=http://hdl.handle.net/10079/bibid/12599233

Questions:

• I will use the bacrb and bacref to determine whether to display Rare Books and Manuscripts or Reference Library. Is that sufficient?
• which 852s subfields are used to pull together the call number?
• The 3rd line in above holding display I believe are from the 541c. Many don't have 541, will this line just be omitted from these?
• The aeon request has a mfhdID, which is retrieved from endpoint: https://libapp-test.library.yale.edu/VoySearch/GetBibItem?bibid="+bibid. Is this a required field for the aeon request? If so how to retrieve the alma equiv?
• The aeon request has an EADNumber with a handle pointing to orbis holding. Is this a required field for the aeon request? If so what should it be in the alma environment?

[flapka]

@yulgit1 Thanks for posing these (important) questions.

1. Yes, the bacrb or bacref* in 852 subfield $c will be the determinant.
2. Call numbers = 852 subfields $k, $h, $i, and $m, in that order. We definitely want to omit any others (esp. subfield $x, which is non-public).
3. Yes, Something like 2/3 or 3/4 of rbm records will have 541 $c, but for the rest the line will be omitted. This is true with the Voyager dataset too.

[flapka]

4. Yes, I think the MFHD ID is a required element for Aeon requests. It is the same as the subfield $8 values in fields 852, 541, etc. -- Probably there's no reason to index this value, unless it's hard to construct the Aeon request URL without it indexed.

[flapka]

5. Good catch. The handle is not required for an Aeon request transaction. Last I heard, YUL was still deliberating on what to do with handles for the Alma migration. They may be replaced with something else -- perhaps a simple Quicksearch link based on the MMS ID? Still TBD. In the long run, it'd be nice to populate this field with whatever is used as handle equivalent, but that's not a day 1 requirement; hopefully my successor can supply the info when appropriate.

[yulgit1]

I've created an new xslt for alma harvest, tweaking the current one used with voyager. https://git.yale.edu/ermadmix/ycba_xslts/blob/master/marc-alma-drupal-ycba.xsl

and tested it with the following (comparing alma with orbis):

Independent record with 541: https://alma1.s3.us-east-1.amazonaws.com/harvest1/00/9933493003408651.xml https://libapp.library.yale.edu/OAI_BAC/src/OAIOrbisTool.jsp?verb=GetRecord&identifier=oai:orbis.library.yale.edu:3349300&metadataPrefix=marc21

BW with multiple holdings: https://alma1.s3.us-east-1.amazonaws.com/harvest1/68/99111109683408651.xml https://libapp.library.yale.edu/OAI_BAC/src/OAIOrbisTool.jsp?verb=GetRecord&identifier=oai:orbis.library.yale.edu:11110968&metadataPrefix=marc21

The only difference is a new credit_line_ss, and call_number_ss, and a different url_ss.

   <credit_line_ss>22207462620008651|Yale Center for British Art, Paul Mellon Collection</credit_line_ss>
   <credit_line_ss>22207462590008651|Yale Center for British Art, Paul Mellon Collection</credit_line_ss>
   <credit_line_ss>22207462650008651|Yale Center for British Art, Paul Mellon Collection</credit_line_ss>
   <call_number_ss>22207462620008651| N7630 .C67 1800+ Copy 2 Oversize</call_number_ss>
   <call_number_ss>22207462590008651| N7630 .C67 1800+ Copy 3 Oversize</call_number_ss>
   <call_number_ss>22207462650008651| N7630 .C67 1800+ Copy 1 Oversize</call_number_ss>

I made the url_ss to a not yet existing handle, we can ignore for now, or change later: old:

http://hdl.handle.net/10079/bibid/11110968

new:

http://hdl.handle.net/10079/alma/99111109683408651

Next steps will be to create a test solr core, and run the full gamut from alma harvest to solr index. I'm assuming the ID for this will now be the alma mms id rather than the voyager bibid.

[yulgit1]

Online catalog solr index from alma: https://ciaindex2.britishart.yale.edu/solr/#/ycba_alma1/ (requires basic auth, I can give u pw if interested)

 "Reference Library",39331,
 "Rare Books and Manuscripts",21304,
 "Archives",41]},

Includes indexed holdings like:

"credit_line_ss":["22283507880008651|Yale Center for British Art, Paul Mellon Collection"],
"call_number_ss":["22283507880008651| ND497.R66 A2 1773"],

And identifiers like: "id":"alma:9977721933408651",