...
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Agenda Outline
Doodle Poll (closed):
...
http://www.doodle.com/8bqama5tym9ny6wd
...
Time:
...
11:00am
...
-
...
1:00
...
pm
...
EDT
...
Date:
...
Tuesday,
...
July
...
17,
...
2012
...
Location:
...
CIB
...
207A
...
and
...
Webex
...
Webex:
...
...
.
...
Tel:
...
1-408-600-3600
...
(mtg
...
ID-
...
625 833
...
990
...
)
...
Invitees:
...
John
...
Pillans,
...
Docstore,
...
IU;
...
Mechael
...
Charbonneau,
...
Gary
...
Charbonneau,
...
Jackie
...
Byrd
...
-Describe/Cataloging,
...
IU;
...
Chris
...
Case
...
-
...
Deliver,
...
Systems
...
Integration,
...
FL;
...
Tod
...
Olsen
...
(for
...
Frances),
...
Chicago;
...
Michelle
...
Suranofsky
...
-
...
Editors,
...
Describe,
...
Lehigh;
...
Doreen
...
Herrold
...
-
...
Editors,
...
Lehigh;
...
Jeff
...
Fleming
...
-
...
NCIP/Systems
...
Integration,
...
Duke;
...
Peri
...
Subramanya,
...
HTC;
...
Nianli
...
Ma,
...
Dan
...
Sweeney,
...
Kathy
...
Gerdink,
...
Patty
...
Mescher
...
Agenda:
...
- Instance
...
- Schema
...
- Paired
...
- Values/Sequencing
...
- Issue:
...
- Does existing
...
- Schema
...
- account
...
- for “paired fields” sufficiently,
...
- for
...
- examples
...
- such
...
- as
...
- Marc
...
- 583
...
- $n$o
...
- via
...
- <linkage>
...
- and
...
- <fieldLinkAndSequenceNumber>
...
- that
...
- are
...
- commented
...
- out?
...
- COMMENTS:
...
- data
...
- storage
...
- as
...
- data attributes vs.
...
- data
...
- string
...
- is
...
- a.o.k,
...
- as
...
- long
...
- as
...
- presentation
...
- is
...
- based
...
- on
...
- functional
...
- requirements.
...
- Action
...
- Item:
...
- Linkage
...
- that
...
- has
...
- been
...
- commented
...
- out
...
- and
...
- must
...
- be
...
- reviewed
...
- and
...
- then
...
- restored.
...
- Should display/edit
...
- of
...
- Call
...
- Numbers
...
- -
...
- parsed
...
- to
...
- 4
...
- elements,
...
- be
...
- modified
...
- in
...
- how
...
- it
...
- is
...
- stored?
...
- Users
...
- need
...
- to
...
- copy
...
- the
...
- entire
...
- call
...
- number
...
- and
...
- copy
...
- and
...
- paste
...
- -
...
- do
...
- not
...
- want
...
- to
...
- copy
...
- a
...
- piece
...
- of
...
- the
...
- call
...
- number
...
- to
...
- specific
...
- fields.
...
- prefix
...
- and
...
- suffix
...
- very
...
- local
...
- -
...
- should
...
- not
...
- be
...
- copied
...
- from
...
- OCLC
...
- -
...
- we
...
- need
...
- to
...
- determine
...
- if
...
- we
...
- can
...
- split
...
- the
...
- call
...
- number
...
- from
...
- item
...
- (classification/item)
...
- is
...
- there
...
- a
...
- real
...
- business
...
- case
...
- to
...
- split
...
- these
...
- at
...
- the
...
- database
...
- layer
...
- (classification
...
- team
...
- may
...
- determine
...
- the
...
- real
...
- need
...
- for
...
- this)
...
- Action
...
- Item:
...
- Mechael:
...
- Provide
...
- use
...
- cases
...
- -
...
- Patty/Dev
...
- Team
...
- -
...
- options;
...
- Jeff:
...
- easier
...
- to
...
- keep
...
- separate
...
- -
...
- we
...
- can
...
- combine
...
- when
...
- needed
...
- (storage)
...
- Legacy
...
- Data
...
- Issue:
...
- is
...
- this
...
- about
...
- complexity
...
- of
...
- mapping
...
- old
...
- data
...
- to
...
- new
...
- structure?
...
-
- challenge - pulling from mark holding to the instance record for legacy data- ; User Interface is challenging for the amount of data that needs to be entered for instance vs. holdings.
- Editor User Interface - take a look and determine what we can do
- And how/where to account for “extension elements”? HOLD until further notice......
-
...
- MFHD
...
- mappings
...
- Issue:
...
- is this
...
- same
...
- as
...
- above
...
- or
...
- more
...
- about
...
- renaming
...
- and
...
- reordering
...
- of
...
- key
...
- elements
...
- that
...
- occurred
...
- in
...
- OLE
...
- instance,
...
...
...
- Omitted/missing
...
- data
...
- elements
...
- 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> . (COMMENT:
...
- These
...
- may
...
- all
...
- have
...
- a
...
- functional
...
- story
...
- tied
...
- to
...
- them.
...
- This
...
- is
...
- back
...
- to
...
- the
...
- Mark
...
- Holdings
...
- support)
...
- COMMENT:
...
- Jeff:
...
- 850
...
- -
...
- 860
...
- -
...
- paired
...
- fields
...
- -
...
- looking
...
- at
...
- how
...
- this
...
- is
...
- going
...
- to
...
- convert
...
- to
...
- instance
...
- schema
...
- -
...
- this
...
- will
...
- be
...
- related
...
- to
...
- our
...
- overall
...
- Mark
...
- holdings
...
- support
...
- decisions.
...
- Jeff
...
- has
...
- documentation
...
- on
...
- this
...
- mapping.
...
- Proposed Solution Discussed:
- Refactor Cost:
- Configuring "extension"
...
- elements
...
- (for
...
- UI,
...
- indexing)
...
- 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?)
- Location elements- in Items, Hierarchy
- 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. COMMENT: we are in agreement with the 5 level limit. COMMENT: LOCATION is at the ITEM level - further discussion...especially from a user interface perspective and how the location will be updated/managed between holdings and items. This is a frequent activity for changing location of several hundred records at one time. (XML for each record, modified and imported back)
- Bib-Instance
- Item linkages
- Issue: what/how is OLE using unique identifiers to support NCIP, Discovery layer-Bib Numbers in OLE-Email thread
- UUID in docstore is not a preferred number reference - Need an additional sequential number tied to the institutions legacy numbering system for bib records
- COMMENT: This additional field should be additional requirements for DocStore. Requirements: Jeff/Tod/John - Mechael & Gary (Infrastructure? - Functional side of house representation? - Patty follow-up)
- Issue: what/how is OLE using unique identifiers to support NCIP, Discovery layer-Bib Numbers in OLE-Email thread
- Item linkages
Technical Implication Issues/Review
Functional Implication Issues/Review
Reference Documentation
- Instance 9.x
- Docstore: summary "not yet completed"
- See all related Google Docs-Working files: questions, schema mapping, MFHD comparison for next Schema Iteration; SME comments from May 16th Instance demo
- OLE Technical Documentation (wiki)
- OLE DocumentStore (Docstore Architecture Model)
- OLE Instance- Docstore
- OLE Bibliographic Documents - Docstore
- Search Documentation
- NOT AT THIS MEETING- Future Discussion Topics or Issues --to be Moved to Another Venue
- DocStore
- Loading Legacy Data; a follow-up to design discussions in June, with John P concerns and recommendations
- Search strategy: SOLR vs KNS (for how/where to store and create indexes- combined bib/instance/transactional data)
- Metadata storage and updating
- Discovery layer
- bib Links or identifiers (discovery layer)
- data transformations vs literal mappings
- Related Issues/Framework issues:
- Editors- esp Combined? Linking from Search UIs
- Editors/other extensible or configurable UIs
- Configurable Indexes, sorts, search fields, facets
- Technical or UI framework
- DocStore