wp 3: standardisation of shared metadata mode of operation –all partners are involved –building...
TRANSCRIPT
WP 3: Standardisation of shared metadata
• Mode of operation– All partners are involved – Building on practice outside the project
• Achievements of Year 1– The ENRICH conceptual model– Schema, documentation, test cases
• Plans for Year 2– Tools development– Data migration
WP3 : Modus Operandi
• No re-invention of the wheel: ENRICH is built upon existing standardisation efforts
– MASTER (1999-2002) ; TEI P5 (2005-)
• Reflect actual practice: ENRICH is driven by actual user needs
– Survey of different applications of MASTER(+)– Cross-partner synthesis and discussion
• Support an integrated system: All aspects of a digital edition are described by the ENRICH schema
WP3: what we did -1• Reviewed differences between TEI P5 and
Master+– Theoretical exercise, but essential– All differences could be resolved, either by
constraining Manuscriptorium practice, or by adapting P5 proposals
• Reviewed actual praxis in a wide sample (1000+) of existing manuscript description records in many formats
– On-going work, leading to development of migration tools
– Identified common core of practice, much smaller than potential of existing TEI schema
WP3 – What we did 2
• TEI P5 is designed to support a huge range of document types and encoding practices
• For ENRICH, we defined a much more constrained subset, reflecting actual practice
– e.g. constraining value lists, reducing structural choices, reducing scope for redundancy
Some example changes
MASTER+ ENRICH<p> elements required everywhere <p> required only if multiple<g> not available in text <g> available everywhere<msHeading> permitted <head> deprecated
<altName> used ambiguously <msName> or <altIdentifier> distinct
WP3 - What we did 3
• The ENRICH schema is formally defined using the TEI ODD system
• This XML vocabulary allows us to generate automatically:– full multilingual documentation– formal schemata in DTD, RelaxNG
or W3C Schema• Its TEI-conformance makes it
accessible to many other projects
WP3: scope of the schema
• The ENRICH schema provides a formal way of recording information about a manuscript resource, expressed in XML
– Such records can be managed and stored independently of the resources they describe
• It also provides a formal way of encoding in XML:
– A detailed transcription of the resource– Information about images (etc) of the resource– Information about real-world entities associated
with the resource, i.e. people, places and events
WP3: challenges and how we overcame them
• Synchronising ENRICH requirements with TEI P5
– We worked closely with TEI Council which was revising the manuscript module at the same time
• Reaching consensus among partners– We worked closely with AIP to ensure that
Manuscriptorium was able to support the full complexity of TEI P5
– We were able to use the TEI I18N features to produce reference documentation in French, Italian, Spanish as well as English (other languages will follow)
WP3 – outreach and training
• We have tested the ideas behind the ENRICH schema in many different training contexts
• We have produced a suite of training materials covering
– Basic ideas of XML markup– TEI modules for metadata, basic document
structure, manuscript description and transcription, persons and places, facsimiles, nonstandard writing systems...
WP3 conversion tools
• We have developed a suite of XSLT stylesheets and associated workflows to convert between existing metadata formats and ENRICH
• So far we have worked with – MASTER (+)– EAD– MARC
• In the next phase of the project we plan to develop the ‘ENRICH Garage’ concept...