Original notes:

• Harvesting / exporting of records from ILS
  • bibliographic, holdings, authority, item if available and reasonably persistent
  • ids should be included where needed
  • we'll need to specify in more detail what info should go here
  • may want to export availability info (even if it changes fast?)
  • formats: MARC, marcxml, possibly others like MODS: issues of standard formats for sub-holdings data
  • Also may need non-MARC information associated with a bibliographic record (ex: order information, holds information, item information; licenssing/rights information)
  • record control information (ex: date created or cataloged) [ejl] may be important
  • think if there's any non-ILS data that's especially important (e.g. digital repository metadata records)

Use cases:

• Build a duplicate record set indexed in interesting ways
• Export into third party indexing services (e.g. Google)
• Create an aggregated index (your catalog, your IR, your
  favorite licensed DBs if you can get their data, etc.)
• Identifying added, changed and deleted records and exporting those
• Selective export/harvest based on properties (e.g. video catalog, records with rights to export)
• Build index (e.g. subject maps, name directories) based on authority records
• Export just bib records vs. exporting beyond just the bib record (e.g. holdings, item status, etc.)
• Export licensing information (where this is isn't clear, but may be in ILS OPAC or acq. model, or provided by ERMS)
• May want to get all the holdings/item data for a list of records (could be realtime, could be aggregated)

Notes:

• Rights issues may apply; might not be able to export everything.
• Note that keeping track of IDs, and understanding their lifespan, may be important. E.g. bib ids, authority ids, item record ids or barcodes. This is often outside the standard MARC records themselves.
• There may be multiple formats even of the same type of recrds. (E.g. some repos or ILS's might have some bib records as MARC, some as DC, some as MODS). You could either pass them as they are, or you can have the ILS/server normalize on the way out.

Functions:

GetBibliographicRecords

GetExpandedRecords

List of possible types of item information that might be desired in an expanded record from NCSU work on union catalog. Some of these may not be available in all ILS item records: 

• Status (available, checked out, library use only)
• Whether or not it circulates may be a separate flag
• Date Due (may not be available from NCCU and NCSU)
• Library (usually a physical building)
• Location (most specific physical location, i.e. stacks)
• Call Number
• Call Number Scheme (if using this for a call number facet, will need to know if it's LC / SuDoc / NLM, etc.)
• Format
• Total Number of loans
• Barcode
• Item Notes
• Item creation date
• Item last activity date
• Other special information - most ILSs will have some unique item data elements, for example, SirsiDynix has item category 1 and item category 2, which we use to label things like reference materials or government documents

NCIP item object is composed of these data elements:

• Bibliographic Description
• Circulation Status
• Electronic Resource
• Hold Queue Length
• Item Description
• Item Use Restriction Type
• Location
• Physical Condition
• Security Marker
• Sensitization Flag

There is also a z39.50 Holdings Schema (referenced in the Bath Profile) at http://www.loc.gov/z3950/agency/defns/holdings.html. Looking at it, we may want to create/use separate recommendations for expressing item information and circulation information.

Piece

CircInfo

ReservationInfo

ServiceInfo

 PhysicalFormInfo

GetBibAndHoldingsRecords

GetHoldingsRecords (needs to include bib ids if not already present)

(for all, or for a given set of bib ids)

Parameters:

• with or without date limitation (i.e. incremental or non-incremental)
• with or without an explicit set of bib ids (may also want realtime, but may
  be useful as "batch" operation if there are a lot of these)
• with or without selection filters (e.g. video records). Too complicated to
  put in now?)

The functions differ by how wide-ranging are the records

• bib data only
• bib + holdings + item + circulation (w/ acquisition e.g. on order?)
• bib + holdings only
• holdings only

Return values: Set of ids &
(MARC or MODS or DC or whatever for bibs)
(if doing more than bib records, need some way of containing all the pieces
that go with a particular item. Might need some sort of container objects or
XML elements)

Exceptions:

Side effects:

Rationale:

Detailed description:

Other notes:

May not support all of these.
May limit who is allowed to get these, how often, or how aggressively to throttle access.
Some large-scale vendor systems may not perform well enough to support some or all of these options in practice.

Bindings:

OAI-PMH

Vendor export function (perhaps with a standard veneer in front)

Object library?

GetAuthorityRecords

Much the same, but in a different return format
(e.g. MARC authorities, possibly as marc21 xml, MADS)

Bindings:

OAI-PMH
Object library?

GetLicensingInformation? (Would this be a batch export function?)

Who will work on expanding this: John, Terry, Dianne, David B