[DCRM-L] access restriction data (Aeon)

Mon May 13 11:19:52 MDT 2019

Erin,

I believe YUL’s IT department has confirmed that option 3 would work – if all the related procedural complexities were worked out.  The item_type_code and item_type_name data values are certainly available through the API, as in this example:

https://libapp.library.yale.edu/VoySearch/GetAllMfhdItem?bibid=1166765

Francis

From: DCRM-L [mailto:dcrm-l-bounces at lib.byu.edu] On Behalf Of Erin Blake
Sent: Monday, May 13, 2019 12:57 PM
To: DCRM Users' Group <dcrm-l at lib.byu.edu>
Subject: Re: [DCRM-L] access restriction data (Aeon)

Oooh! Is option 3 (Item Type) something that's actually known to work, or are you just wondering? We don't currently use the Voyager API with Aeon (but will after we upgrade to TomCat Webvoyage), but we'd been assuming we'd be able to pull from the 506 in the mfhd.

If the 506 in the mfhd won't pass through, we definitely could use an Item Type -- currently we have a grand total of three item types (Open stacks, Vault, Online resource) and none of them are actually used for anything at the moment.

Cheers,

Erin.

----------------
Erin Blake, Ph.D.  |  Senior Cataloger  |  Folger Shakespeare Library  |  201 E. Capitol St. SE, Washington, DC, 20003  |  eblake at folger.edu<mailto:eblake at folger.edu>  |  office tel. +1 202-675-0323  |  www.folger.edu<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.folger.edu&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C686d03a044164965036308d6d7c425ac%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636933634796914701&sdata=ypSFbPmqFl9lfFMbOw793GNVGpNM1UT4%2FWuEa5JRwsY%3D&reserved=0>

On Mon, May 13, 2019 at 11:14 AM Lapka, Francis <francis.lapka at yale.edu<mailto:francis.lapka at yale.edu>> wrote:
For those who have implemented Aeon, I’m keen to hear how you pass access restriction information from your OPAC to Aeon (not from finding aids).

As Yale considers new procedures, at least three options come to mind:

  1.  Record the restriction in the 506 field<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fbibliographic%2Fbd506.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C686d03a044164965036308d6d7c425ac%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636933634796914701&sdata=z9XC9X6MZtZttXyIlgXJ160ZRuA9nfnRL4r74YivWYQ%3D&reserved=0> of the Bib record. The 1st indicator provides a machine-actionable value; the text provides an elaboration. Drawback: When we have more than one copy, a 506 in the Bib may inadequately specify the copy to which it applies (in terms of machine actionability, at least).

  1.  Record the restriction in the 506 field<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fholdings%2Fhd506.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C686d03a044164965036308d6d7c425ac%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636933634796924705&sdata=EpQUB1UCAuBmv1RZb2alIYcAGaMZNFhQMJvHf7SFQFY%3D&reserved=0> of the Holdings record. This allows us to specify a copy. But: [a] it may inadequately specify the volume or part to which it applies (in terms of machine actionability, at least), and [b] the Holdings 506 is not passed to our OPAC, nor is it made available in our Voyager API (is the same true for other Voyager institutions?)

  1.  Record the restriction by creating (or using) a separate Item Type (in the Voyager item record). If starting a catalog from scratch, this might be the most logical approach. It’s unclear if we could do this at Yale, because we have so many procedures tied to the existing item types.

All advice is appreciated.

Thanks,
Francis

Francis Lapka  ·  Senior Catalogue Librarian
Department of Rare Books and Manuscripts
Yale Center for British Art
203-432-9672  ·  francis.lapka at yale.edu<mailto:francis.lapka at yale.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserver.lib.byu.edu/pipermail/dcrm-l/attachments/20190513/f106701d/attachment-0001.html>