Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Date
Attendees
Discussion items
Time | Item | Who | Notes |
---|
| Joint Resource Management/Metadata Management Discussion on the Resource Management Data Domains Model | Cate Boerema (Deactivated) | - Metadata Concept:
- Heirarchy:
- Instance - describes resource holding
- Codex: Minimal set of metadata; instance-level; e.g. resource name, identifier (ISSN)
- Detail record: specialized descriptive record; data will vary based on type of resource; e.g., other identifiers (OCLC numbers)
- Where do instance records come from?
- manually entered
- distilled from a local record such as MARC
- exported record may not be the same as the local record
- Accessed via external kb
- FOLIO Instance Records
- FOLIO bridge module will be necessary for external kb, mapping/cross-walks (work has to be done by provider)
- Question: Evaluation process for external kbs? A standard?
- External kb access will vary - could be read-only, also read/write
- Will be other ways to integrate for those that are not set up with the bridge module
- How are local instance records edited?
- Local records are fully editable
- Don't know where editor will live yet
- Edits do not impact linked, source records
- Can preview/generate new records in MARC
- Source record can be modified in their native formats
- FOLIO record is still format agnostic
- Edits will only sync with FOLIO record if explicitly requested by user
- FOLIO will notify user of conflicts with sync
- **Some terminology issues with the slides**
|
| | | |
Action items