Aeon links

[edgartdata]

Check with Matthew and Ed if we should make the locations of items that are not on view available through Aeon for the purpose of giving patrons the opportunity to request items in the Study Room. And a related question: would the online collections catalog still only show 'on view' or 'not on view'?

If it is a yes to Aeon, explore how easy it would be to add Aeon links to each individual object record.

Work with Charlotte/P&D on the mapping between the TMS location metadata and the Aeon fields.

Give Eric the Xpath for discrete location to TMS object

[edgartdata]

@yulgit1 Actually I was wrong: LIDO DEV does not carry the discrete location of works of art in the P&D and P&S collections. It only has 'on view' or 'not on view'. So I guess the question is now: @EdwardTown1 is it okay for P&D staff to search the location in TMS based on teh accession number of the requested object in Aeon?

[edgartdata]

@KraigBinkowski @flapka It might be helpful to get a sense of the tentative timeline for Aeon roll out for P&D and Archives.

[flapka]

I'm attaching three documents that were part of our discussions with YUL IT in 2018. These are primarily for the benefit of @yulgit1 Jay_Terray_email_2018.pdf aeon_request_config.docx aeon_holdings_helper.rb.docx

[flapka]

The requesting mechanism seems relatively simple, though @yulgit1 shouldn't hesitate to let me know if I'm underestimating it.

An example. To request this item in Orbis: http://hdl.handle.net/10079/bibid/13709335

The Aeon request link is based on this snippet of html:

<a target="_new" href="https://aeon-mssa.library.yale.edu/aeon.dll?Action=10&amp;Form=20&amp;Value=GenericRequestMonograph&amp;Site=YCBA&amp;CallNumber=N7645%20.L48%201889&amp;ItemTitle=Warwick%20Brookes'%20pencil-pictures%20of%20child%20life%20%2F&amp;ItemAuthor=Letherbrow%2C%20Thomas%2C&amp;ItemDate=&amp;Format=18%20cm&amp;location=bacrb&amp;mfhdID=13732453&amp;EADNumber=http://hdl.handle.net/10079/bibid/13709335" id="locMap">Request for use in the YCBA Study Room</a>

The parameters are largely based on metadata of the object. The parameters would make use of these Blacklight fields:

• blacklight-callnumber
• blacklight-title_ss
• blacklight-author_ss
• blacklight-publishdate_txt
• blacklight-physical_txt
• [location: would require additional coded data in the Blacklight html – probably not displayed to the public]
• [mfhd: this field is specific to items from Orbis. It is currently not passed to us in our OAI harvests. Will investigate.]
• blacklight-url_txt

Those fields are the starting point. We may have a little bit of wiggle room in what information is included in the rquest, to ensure that the data that gets passed to Aeon is logical from the stand point of P&D.

[flapka]

The screenshot below shows how the catalog data (for the same example named above) gets passed to Aeon:

I think we should have no trouble configuring a passing of data that works well for P&D material.

[edgartdata]

@flapka What would be most helpful for the P&D staff is to have the TMS object location show up in Aeon.

[flapka]

@edgartdata Yes, it should be doable to have the TMS object location show up in Aeon. The easiest way to do this would be to "hide" the location data among the parameters that the catalog passes to Aeon. This is minimal hiding (an attentive patron could parse it in the URL -- though the information will appear nowhere else in the patron view).

I think other mechanisms may also be possible (based on YUL experience), if the above is insufficient.

[flapka]

Among the parameters passed to Aeon (for library collections) is the mfhdID -- i.e., the record number for each copy of a book. Our records in Blacklight don't include the mfhdID data, because it is not available in the OAI-PMH service. The mfhdID is available, however, by querying the Voyager API. I can envision a routine or two that would make it rather trivial to retrieve this information.

For now, I'm merely including the Voyager API documentation, for when we have the inclination to pursue this development. Voyager_API.pdf

[edgartdata]

@EdwardTown1 @flapka Is this a good opportunity maybe to revisit the visibility of location of P&D items for users of Aeon, i.e. display the full granularity of the items locations in Aeon? I am assuming that it will make things easier for integration of LIDO XML and Aeon but of course we should discuss.

[flapka]

Sure. Happy to discuss this more in one of our upcoming meetings.

[edgartdata]

@edgartdata to set up meeting with Chitra.

[flapka]

@yulgit1 More on the requirements for RB material:

The following is a useful test record, since YCBA has 2 copies of the book and Beinecke has 1: http://10.5.96.187:3000/catalog/orbis:1166765

(In Orbis: https://orbexpress.library.yale.edu/vwebv/holdingsInfo?bibId=1166765)

In the YCBA catalog we'll want the call numbers for the 2 YCBA copies to show up, but not the Beinecke one (already correct in Blacklight). And next to each call number for the YCBA copy, we'll want separate request links or buttons -- so that the patron can specify the copy of interest.

I think this base URL, from the Voyager API, provides the data we need to fulfill our use case, here with our testing record number: https://libapp.library.yale.edu/VoySearch/GetAllMfhdItem?bibid=1166765

At that URL, we want to examine each holding, looking for = bacrb.

For each match, we want to grab two pieces of data:

• mfhd_id
• mfhd_callno

Obviously, it's important that these pairs remain attached to each other (so that each call number is associated with the right mfhd_id).

Since, we need to have the Aeon request associated with the right copy (when we have more than one), it probably doesn't make sense to have the Aeon "Request Item" on a separate line. I suggest that this request text should appear just to the right of the call number (and eventually, perhaps, the P&D access number?).

Our group needs to discuss the request text as well, but as a starter perhaps: "Request for use in the YCBA Study Room"

[flapka]

Also: As we conduct testing, it's probably better to point our Aeon requests to the Dev version. I think the base URL for Dev requests is: https://aeon-2-dev.its.yale.edu/

And here's an example of a full request, to Dev: https://aeon-2-dev.its.yale.edu/aeon.dll?Action=10&Form=20&Value=GenericRequestMonograph&Site=YCBA&CallNumber=Folio%20C%202014%204&ItemTitle=Helmingham%20herbal%20and%20bestiary&location=bacrb&ItemAuthor=&ItemDate=&mfhdID=9799201&ItemInfo4=quicksearch

[edgartdata]

@edgartdata @EdwardTown1 to write a risk memo for Becky to review.

[flapka]

The base URL for Aeon test/dev has changed to: https://aeon-test-mssa.library.yale.edu/

The URL for production is unchanged.

[yulgit1]

@flapka aeon endpoint is now configured to https://aeon-test-mssa.library.yale.edu/

[flapka]

Tentative agreement:

Use the same language as in Orbis for making requests in Blacklight: "Request for use in the YCBA Study Room"

Have this text/link appear directly after each accession no. / call no., perhaps in square brackets.

Underline the link-text, to make it more clear that it is a link.

Also: enable requests only for P&D and RBM (eventually IA).

[flapka]

P&D parameters use a separate template in Aeon. I'll provide more information for Eric.

[edgartdata]

@flapka 2 requests:

• can you give us an example of a RB item with several call numbers?
• how are we handling P&D items location for the staff?

[flapka]

Two examples of RB items with multiple holdings (multiple call numbers):

• Silver bullet: http://10.5.96.187:3000/catalog/orbis:12398790
• Dance of life: http://10.5.96.187:3000/catalog/orbis:1341377

I don't fully understand your 2nd question (handling P&D items location for the staff). Could you elaborate?

[yulgit1]

@flapka re: P&D, what the parameters should be (including correct URL host). If you provide parameter values (any P&D example object will do) I can derive where to get them:

https://aeon-test-mssa.library.yale.edu/aeon.dll?
aeon += "Action=#{action}&" aeon += "Form=#{form}&" aeon += "Value=#{value}&" aeon += "Site=#{site}&" aeon += "CallNumber=#{callnumber}&" aeon += "ItemTitle=#{title}&" aeon += "ItemAuthor=#{author}&" aeon += "ItemDate=&" aeon += "Format=#{physical}&" aeon += "Location=#{location}&" aeon += "mfhdID=#{mfhd}&" aeon += "EADNumber=#{url}"

[yulgit1]

RB aeon links with call number addressed with: https://github.com/ycba-cia/blacklight-collections2/commit/76e426afbdfb56dffc202e7e9865ff959348f888

[flapka]

@yulgit1 To the P&D question, provisionally:

Example P&D record: http://10.5.96.187:3000/catalog/tms:10028

aeon += "Action=#{action}&" 10

aeon += "Form=#{form}&" 20

aeon += "Value=#{value}&" GenericRequestMonograph

aeon += "Site=#{site}&" YCBA

aeon += "CallNumber=#{callnumber}&" [Accession Number] B1977.14.5860

aeon += "ItemTitle=#{title}&" [Title] Boat by a Lake

aeon += "ItemAuthor=#{author}&" [Creator] Joseph Barber, 1757–1811, British

aeon += "ItemDate=&" [Date] undated

aeon += "Format=#{physical}&" [Medium?] Watercolor on medium, slightly textured, cream wove paper

aeon += "Location=#{location}&" [the hidden P&D location] YCBA (1080 Chapel), YCBA, 222, C 8, B- 1,

aeon += "mfhdID=#{mfhd}&" [n/a]

aeon += "EADNumber=#{url}"\ [n/a]

[yulgit1]

@flapka - location is not indexed. Is there a place to retrieve this info, or should it be left blank? I know there were some issues in exposing this anyway.

[flapka]

@yulgit1 @edgartdata I was under the impression that P&D location info [1] was either currently available deep in the LIDO XML or the RDF served somewhere; or [2] could be made available in this manner. Alternatively, might it be sensible to index such location information, even if we might have to create a new field to do so? I defer to Emmanuelle, Ed, et al.

I briefly chatted with Charlotte about the issue of serving location information to Aeon and she was curious whether it would retrieve the TMS "current location" or the TMS "home location"-- and I couldn't say one way or the other.

[yulgit1]

@flapka @edgardata @KraigBinkowski I excluded location from P&D for the time being. Please let me know if otherwise is ok for each of the collections. https://github.com/ycba-cia/blacklight-collections2/commit/fc72be0809cc96fdb7ff7cbfbe7a0d62d650928b https://github.com/ycba-cia/blacklight-collections2/commit/263015b2bc3964246923ee594c89c49916a6e9d3

[flapka]

Copied below is an example of a P&D object requested through Blacklight. The results are generally promising, I think. There are two changes that we can make to improve the data passed:

1. Find a way to pass location data for P&D objects
2. For the "&EADNumber=" parameter, pass the URL for the object record. This URL will then show up in the Aeon "Handle" field. I left out this instruction before.

[flapka]

@yulgit1 @edgartdata There is provision in the LIDO XML to have location information -- already in place for paintings & sculptures. EDG will work with David to have the P&D location passed to the LIDO XML, while handling location information differently (?).

EDG will work with Eric.

[yulgit1]

EADNumber added: https://github.com/ycba-cia/blacklight-collections2/commit/638c63473aeed67de7653ee208f9be4df8c16803

[edgartdata]

@flapka @yulgit1 I checked with P&D and Current Location is what needs to be in Aeon. @yulgit1 you probably need to index these current locations (when they come through for P&D in LIDO XML) so as to push to Aeon from the BlackLight SOLR index?

[yulgit1]

@edgartdata which field(s) in the LIDO? We had discussed using: lido:label="On view or not" there is also lido:label="UnitType" lido:label="SubSite

[edgartdata]

@yulgit1 The LIDO element of interest will be from the :

YCBA, 222, C 9, C- 5, [2F, Print Room Note the new label "locaton" for P&D. Right now the same LIDO element is used for P&S with the label "on view, not on view" as you mentioned. David and I will be working on the COBOAT template tomorrow to produce this so hopefully it will be in bac6dev soon for you to test.

[yulgit1]

@edgartdata - Will this replace label="on view, not on view", or be in addition to it? Is there ever a location given where the item is "not on view" (like on a shelf or in a filing cabinet)? Is this both for P&S and P&D?

There are 2 separate concerns 1) maintaining the "view" or "not on view" facet for P&D and P&S. 2) Having a location to pass to aeon for P&D.

[yulgit1]

@edgartdata @flapka @KraigBinkowski - along these lines, would there ever be ref or rb "on view"? If so where would that information exist? Currently there is no onview facet field for these.

[edgartdata]

@yulgit1 is in addition to label="on view, not on view"

Yes, there are many P&D items that have a location but are not on view. Actually it is the case for 99% of P&D items. The reverse situation, where P&D items are on view in the public galleries, are when they are included in an exhibition.

For P&D items, we don't want to publish their detailed location in BlackLight. We only want their detailed location in the LIDO XML and in Aeon. P&D works should only have 'on view' or 'not on view' in the BlackLight interface.

[edgartdata]

@EdwardTown1 This opens up 2 interesting opportunities:

• print the detailed location of P&S in their detailed records
• if that's not desirable, do we want to add the "on view, not on view" status of P&D and P&S works in their detailed records/pages?

[flapka]

@edgartdata @flapka @KraigBinkowski - along these lines, would there ever be ref or rb "on view"? If so where would that information exist? Currently there is no onview facet field for these.

The RB situation is roughly analogous to PD's. The concept "on view" would apply only to the <1% of items that are temporarily in an exhibition. We don't currently record such a status in the MARC record, but there are a couple of ways we could, if all parties thought this was a desirable outcome.

[KraigBinkowski]

Ref would have none "On View" and in RB case, one could make the argument that a book "on View" is actually less accessible then one not on view, as a book in an exhibition is stuck on one page. But it might be good for the patron to know this.

[edgartdata]

@flapka I do think it would be helpful for when RB items are included in exhibitions.

[yulgit1]

P&D Location added: https://github.com/ycba-cia/blacklight-collections2/commit/b525a390434c08a017d1a5de97757dfc965f29b8

One test rec: http://10.5.96.187:3000/catalog/tms:22809

Full index over the weekend

[edgartdata]

I sent a request to P&D for this item. I did not see the detailed location as a patron, which is great. I sent a message to P&D to know if they got my request fine with location. Not sure where that message went!

[flapka]

Here's how the request appears in the Aeon client software (viewed by staff only). The location successfully appears in the proper place!

[flapka]

And here's how the request appears on the printed (paper) call slips, which Study Room staff will use to retrieve the material. Again, location information shows up properly.

[edgartdata]

@flapka In your first screenshot, the field Location cuts off the last part of the detailed locationfor the shelf!

[flapka]

It does, yes. But evidence suggests that the data is there, if we scroll to the right (since it prints on the call slip). This begs the question: Is it possible (and do we want) to abbreviate the initial bit, i.e. the “YCBA (1080 Chapel), YCBA” so that everything important appears in the width of the field?

Francis

From: Emmanuelle Delmas-Glass notifications@github.com Sent: Thursday, August 1, 2019 4:15 PM To: ycba-cia/blacklight-collections2 blacklight-collections2@noreply.github.com Cc: Lapka, Francis francis.lapka@yale.edu; Mention mention@noreply.github.com Subject: Re: [ycba-cia/blacklight-collections2] Aeon links (#78)

@flapkahttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fflapka&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C3db3f1a57a964d1a18af08d716bcf934%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637002873197607396&sdata=LXfKsT3NhB7hmlTQ%2B7ijs%2Bhq4%2BfZ06JiImVqObWmEWo%3D&reserved=0 In your first screenshot, the field Location cuts off the last part of the detailed locationfor the shelf!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fycba-cia%2Fblacklight-collections2%2Fissues%2F78%3Femail_source%3Dnotifications%26email_token%3DAB2H7U66XYI3HFCRISMR3RDQCM75LA5CNFSM4GTDFWLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3LYMAA%23issuecomment-517441024&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C3db3f1a57a964d1a18af08d716bcf934%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637002873197607396&sdata=UrLy46vpHljM5hB1fv0%2BLX76CZ%2BKC5o0%2FU3deE2gCN8%3D&reserved=0, or mute the threadhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB2H7U6PP22YZQPP2JL5VYLQCM75LANCNFSM4GTDFWLA&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C3db3f1a57a964d1a18af08d716bcf934%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637002873197617393&sdata=6En0ugaY05ZwtqiYDRAULKoDMMI2tF%2BZcPy2%2B7iona8%3D&reserved=0.

[flapka]

We can definitely get rid of YCBA (1080 Chapel). We'll be able to tell if it's not here by the rest of the location information.

Thanks, Charlotte

From: Lapka, Francis Sent: Thursday, August 1, 2019 4:18 PM To: ycba-cia/blacklight-collections2 reply@reply.github.com; ycba-cia/blacklight-collections2 blacklight-collections2@noreply.github.com Cc: Mention mention@noreply.github.com; Padden, Charlotte charlotte.padden@yale.edu Subject: RE: [ycba-cia/blacklight-collections2] Aeon links (#78)

It does, yes. But evidence suggests that the data is there, if we scroll to the right (since it prints on the call slip). This begs the question: Is it possible (and do we want) to abbreviate the initial bit, i.e. the "YCBA (1080 Chapel), YCBA" so that everything important appears in the width of the field?

Francis

From: Emmanuelle Delmas-Glass notifications@github.com<mailto:notifications@github.com> Sent: Thursday, August 1, 2019 4:15 PM To: ycba-cia/blacklight-collections2 blacklight-collections2@noreply.github.com<mailto:blacklight-collections2@noreply.github.com> Cc: Lapka, Francis francis.lapka@yale.edu<mailto:francis.lapka@yale.edu>; Mention mention@noreply.github.com<mailto:mention@noreply.github.com> Subject: Re: [ycba-cia/blacklight-collections2] Aeon links (#78)

@flapkahttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fflapka&data=02%7C01%7Ccharlotte.padden%40yale.edu%7C09660052a85e474f0fb408d716bd666e%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637002875031399517&sdata=E9qJXmt80QMvqQQVhyRYmn%2FRMg2foXEji8rlYjbeCRU%3D&reserved=0 In your first screenshot, the field Location cuts off the last part of the detailed locationfor the shelf!

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fycba-cia%2Fblacklight-collections2%2Fissues%2F78%3Femail_source%3Dnotifications%26email_token%3DAB2H7U66XYI3HFCRISMR3RDQCM75LA5CNFSM4GTDFWLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3LYMAA%23issuecomment-517441024&data=02%7C01%7Ccharlotte.padden%40yale.edu%7C09660052a85e474f0fb408d716bd666e%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637002875031399517&sdata=hoZExlcfEAYDGGhLOqgsZU7lSC%2FeEXoj5N7Gr%2Fs%2BqzE%3D&reserved=0, or mute the threadhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB2H7U6PP22YZQPP2JL5VYLQCM75LANCNFSM4GTDFWLA&data=02%7C01%7Ccharlotte.padden%40yale.edu%7C09660052a85e474f0fb408d716bd666e%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637002875031409508&sdata=3eP46Gd8DFukfVBOeEwCYPaDD0RSI8Ldw4RqKOF%2B4%2BU%3D&reserved=0.

[edgartdata]

I’ll check with David how we can truncate the TMS location label before we send it to XML.

[yulgit1]

@edgartdata @flapka aeon location OK? I spot checked 3:

http://10.5.96.187:3000/catalog/tms:38263 https://aeon-test-mssa.library.yale.edu/aeon.dll?...&Location=YCBA, 223B, C 97, Sh- 8

http://10.5.96.187:3000/catalog/tms:38298 https://aeon-test-mssa.library.yale.edu/aeon.dll?...&Location=YCBA, 223B, C 101, Sh- 2

http://10.5.96.187:3000/catalog/tms:21067 https://aeon-test-mssa.library.yale.edu/aeon.dll?...&Location=YCBA, 222, C 37, Sh- 6

[edgartdata]

@flapka Do you know if it would be possible to show the P&D accession number and TMS objectID in Aeon to the users and staff? Right now the metadata in the user's view is skimpy.

[flapka]

That’s a good question, Emmanuelle. I agree that the data in this view is on the skimpy side (though if you click on the TN you can see a bit more). We could try to advocate for a change via the Aeon Users Group. Anticipating user preferences, I’d guess that the accession number/call number (RB) would be the more desirable of the two fields.

From: Emmanuelle Delmas-Glass notifications@github.com Sent: Wednesday, August 7, 2019 10:22 AM To: ycba-cia/blacklight-collections2 blacklight-collections2@noreply.github.com Cc: Lapka, Francis francis.lapka@yale.edu; Mention mention@noreply.github.com Subject: Re: [ycba-cia/blacklight-collections2] Aeon links (#78)

@flapka Do you know if it would be possible to show the P&D accession number and TMS objectID in Aeon to the users and staff? Right now the metadata in the user's view is skimpy.