|
|
|
Once a library has
completed such an inventory, other steps must be taken towards the
implementation of a metadata management design:
|
|
|
|
(1) Build
library-wide consensus regarding metadata element decisions and generalized
mappings.
|
|
(2) Organize
meetings with stakeholders to discuss the costs and benefits of creating a
MARC metadata repurposing design for the library. Metadata practitioners will
want to use these discussions to demonstrate to their colleagues the value of
stewardship in making tools and resource files more broadly accessible.
Stakeholders’ meetings will present opportunities to begin articulating the
roles and responsibilities of metadata staff and information technology staff
in metadata management.
|
|
(3) Begin to develop
reusable transformation tools that would help to make such a metadata design
logical
|
|
(4) Move from
discussions of a MARC repurposing design to discussions of creating a
library-wide metadata management design. Stakeholders in library-wide
metadata management design will likely be more numerous than those interested
in MARC repurposing design because library metadata activities typically
extend beyond MARC repurposing.
|
|
(5) Investigate the
costs and benefits of taking the creation of a library-wide metadata
management design yet further by investigating the creation of a metadata
management repository of mapping schematics, transformation tools, data
files, and other metadata resources. Creating a metadata repository would
involve treating metadata components as persistent digital objects with
persistent identifiers and descriptive metadata in order to facilitate their
discovery and retrieval through a digital content delivery system. Building
searchable metadata repositories would make it easier for libraries to share
their metadata mapping and transformation resources with each other.
|
|
|
|
Michael will now
talk about what such a repository might look like.
|