[DCRM-L] access restriction data (Aeon)

[Lapka, Francis]

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<http://www.loc.gov/marc/bibliographic/bd506.html> 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<http://www.loc.gov/marc/holdings/hd506.html> 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/728166de/attachment.html>