Page Comparison

...

1. Instance Schema
   1. Paired Values/Sequencing
      1. Issue: Does existing Schema account for "ordered pairings" sufficiently, for examples such as Marc 583 $n$o via <linkage> and <fieldLinkAndSequenceNumber> that are commented out? Should display/edit of Call Numbers- parsed to 4 elements, be modified in how it is stored?
      2. Proposed Solution Discussed:
      3. Refactor Cost:
   2. Legacy Data
      1. Issue: is this about complexity of mapping old data to new structure? And how/where to account for "extension elements"?
      2. Proposed Solution Discussed:
      3. Refactor Cost:
   3. MFHD mappings
      1. Issue: is this same as above or more about renaming and reordering of key elements that occurred in OLE instance, Instance-to-MFHD (brief)
      2. Proposed Solution Discussed:
      3. Refactor Cost:
   4. Omitted/missing data elements
      1. Issue: Values not yet included in 9.x schema – need approach for adding/extending vs what is stored in linked transactional --number of circulations, Donor public display; donor note; price (why needed?); number of pieces (calc); checkin note (or does this stay in tx); other notes. How to use <institutionToWhichFieldApplies> .
      2. Proposed Solution Discussed:
      3. Refactor Cost:
   5. Configuring "extension" elements (for UI, indexing)
      1. Issue: Need to determine approach and future support for adding local "extension elements" provided for in schema at Instance, Holding, and Item levels- need functional and technical scope for 1.0 (what do libraries need, esp if not all MFHD fields provided in initial xml? How extensible and editable will our indexing, Search logic, Search UIs, Editor UIs need to be for early adopters?)
      2. Proposed Solution Discussed:
      3. Refactor Cost:
   6. Location elements- in Items, Hierarchy
      1. Issue: Variation of opinions on use of Temporary, Permanent as Location statuses, instead of repeatable elements named separately; Locations stored in provided 5 level hierarchy (OLE coding 5, but only have 2 levels in sample data, and NCSU wants X levels); location of Location elements at Item level.
      2. Proposed Solution Discussed:
      3. Refactor Cost:
2. Bib-Instance
   1. Item linkages
      1. Issue: what/how is OLE using unique identifiers to support NCIP, Discovery layer-Bib Numbers in OLE-Email thread
      2. Proposed Solution Discussed:
      3. Refactor Cost:

...