Difference between revisions of "ViRR Metadata"

From MPDLMediaWiki
Jump to navigation Jump to search
 
(25 intermediate revisions by the same user not shown)
Line 3: Line 3:
= Bibliographic Metadata =
= Bibliographic Metadata =


'''Describes the intellectual content of the whole work (on multivolume and volume level)'''<br/>
''Describe the intellectual content of the whole work''  
The bibliographic data of the digitized works can be delivered by the institute in MAB2 ("Maschinenlesbares Austauschformat für Bibliotheken"). MAB describes one special data structure which is used on libraries for the exchange of metadata.


Please find the detailed information about the used MAB fields in the [[Mapping_MAB_to_MODS|MAB to MODS Mapping]].
The bibliographic data of the digitized works is delivered by the institute in [http://de.wikipedia.org/wiki/Mab2 MAB2] ("Maschinenlesbares Austauschformat für Bibliotheken") format. MAB is a special data structure which is used in libraries for the exchange of metadata.
For detailed information about the import of MAB data check the [[Mapping_MAB_to_MODS|corresponding mapping]].


= Structural Metadata =
= Structural Metadata =


'''Represents the inherent structure of the complete work'''
''Represents the inherent structure of the complete work''


Structural metadata may either focus on
Structural Metadata in the context of the ViRR application describe the''' logical structure''' of a work.
# Logical structure: --> we will use for ViRR
 
#* Reflects the division of the work into its constituent parts
* Reflects the division of the work into its constituent parts
#* Is independent from the physical carrier medium
* Depends on the physical carrier medium
#* Examples:
* Special case: An article begins in one work and continues in a second work (one structural element split in two works)
#** Book: chapter/law->paragraph
 
#** Prose: section->paragraph
Further understandings of structural metadata which might be addressed at a later stage:
#** Lyrics: canto->stanza->line etc.
* Physical structure:  
#* In the [http://dfg-viewer.de/fileadmin/groups/dfgviewer/zvdd_mets_profile_005.pdf ZVDD METS Profile] most information about the books is storred in the logical strucMap like following information about the ViRR books
** Reflects the layout/arrangement of the text on a specific physical artefact
#*# e: einband (always e1-e4, two for the front cover and two for the back cover)
** Might differ for different physical carrier mediums of the same (intellectual) work
#*# v: vorgebundene, nichtbedruckte Seiten (always after the front cover)
 
#*# d: derivate (content pages)
* Other structural information
#*# n: nachgebundenen Seiten (always after the content pages)
** Dependent on the mark-up language of the transcription (e.g. TEI), other information about the text can be attached, e.g. semantic or syntactic information, incl. linguistic categorizations (clause, morpheme, part-of-speech) or narrative structure (e.g. theme). See [http://www.tei-c.org/About/Archive_new/ETE/Preview/driscoll.xml TEI-Levels of Transcription].
# Physical structure:  
#* Reflects the layout/arrangement of the text on a specific physical artefact
#* Might differ for different physical carrier mediums of the same (intellectual) work
#* Examples:
#** Books: volume->page->line
# Other structural information
:: Dependent on the main research question and the mark-up language of the transcription (e.g. TEI), other information about the text can be attached to the transcription, e.g. semantic or syntactic information, incl. linguistic categorizations (clause, morpheme, part-of-speech) or narrative structure (e.g. theme). See [http://www.tei-c.org/About/Archive_new/ETE/Preview/driscoll.xml TEI-Levels of Transcription].


'''Note:''' It can be happen that in one book is part 1 of an article and the following part 2 is in another book! But within one book, the structure is always hierarchically.


=== List of structural element types ===
=== List of structural element types ===
Based on the requirements from the institute, on [[Goobi]] and on the [http://dfg-viewer.de/profil-der-strukturdaten/ profile of the structural data] from the [[DFG Viewer]].
Based on the requirements of the institute, gathered from [[Goobi]] and [[DFG Viewer]].


{| border="1"
{| border="1"
|width="400pt"| '''Basic'''
|width="400pt"| '''Basic'''
|colspan="2" width="800pt"| '''Enhanced'''
|width="400pt"| '''Enhanced'''
|width="400pt"| '''Journalproject'''
|-
|-
| <pre>
| <pre>
Line 63: Line 56:
* Vorwort (preface)
* Vorwort (preface)
* Widmung (dedication )
* Widmung (dedication )
* Andere Strukturen (other)
 
</pre>
</pre>
| <pre>
| <pre>
Line 87: Line 80:
* Interpretation (interpretation)
* Interpretation (interpretation)
* Karte (map)
* Karte (map)
</pre>
|width="400pt"| <pre>
* Kolophon (colophon)
* Kolophon (colophon)
* Komposition (composition)
* Komposition (composition)
Line 111: Line 102:
* Werbung (advertisement)
* Werbung (advertisement)
* Zwischentitelblatt (title page in-between)  
* Zwischentitelblatt (title page in-between)  
 
</pre>
|width="400pt"| <pre>
* Sammelrezension (Collective review )
* Miszelle (Miscellany)
* Gesetzgebung (Legislation)
* Sonstiges (Other)
</pre>
</pre>
|}
|}
* Currently, each structural element type can have all descriptive metadata as listed below. This could be restricted (based on the Idea "genre specific entry mask"), but that will mean a lot of specification work on the institutes side and on our side (perhaps the [https://zim01.gwdg.de/repos/smc/trunk/03_Functional_Description/02_Scenarios_Concepts/Concepts/Faces/05_Goobi_Documentation documentation from Goobi] can be helpful).
* The list will not be structured in the user interface, but displayed alphabetically (meeting outcome).--[[User:Kleinfercher|Friederike]] 14:45, 7 May 2009 (UTC)


= Descriptive Metadata =
= Descriptive Metadata =
'''Describes the intellectual content of the structural elements of one book''' <br/>
''Describe the intellectual content of the structural elements of a work'' <br/>
'''Metadata about the structural elements''' (can be restricted based on the type of the structural element, e.g. a ToC does not have a author, ...)<br/>
Please view [[ESciDoc_Application_Profile_ViRR-Element|ESciDoc Application Profile ViRR-Element]] for detailed information.


{| border="1"
{| border="1"
|width="200pt"|'''Label (of [[ViRR_Application_Profile|AP]])'''
|width="200pt"|'''Label (according to [[ViRR_Application_Profile|ViRR Application Profile]])'''
|width="250pt"|'''Description'''
|width="250pt"|'''Description'''
|width="400pt"|'''MODS'''
|width="400pt"|'''MODS'''
Line 223: Line 214:


"''Information necessary to allow a repository to manage the object: this can include information on how it was scanned, its storage format etc (often called technical metadata), copyright and licensing information, and information necessary for the long-term preservation of the digital objects (preservation metadata)''" from [http://www.odl.ox.ac.uk/metadata.htm Metadata in the Oxford Digital Library].
"''Information necessary to allow a repository to manage the object: this can include information on how it was scanned, its storage format etc (often called technical metadata), copyright and licensing information, and information necessary for the long-term preservation of the digital objects (preservation metadata)''" from [http://www.odl.ox.ac.uk/metadata.htm Metadata in the Oxford Digital Library].
* Copyright License
*: The digitized works should become public domain, thus they are free for further usage. This should be expressed via a copyright license/statement specified with each digital object, e.g. CC ShareAlike ([http://creativecommons.org/about/licenses Overview on Creative Commons licenses]). The rights statement should be machine readable as well ([http://web.resource.org/cc/schema.rdf Creative Commons RDF schema]).
* Technical Metadata
*: One component of the eSciDoc framework called JHOVE is able to extract all technical metadata currently saved in the pictures.


* '''Human readable''' Copyright & License are described [[VIRR_Copyright_and_Disclaimer#Urheberrecht_des_Inhalts | here]].
* '''Machine readable''' Copyright & License should be integrated into the ViRR application profile (MODS:copyInformation, accessCondition).
* '''Technical Metadata''', how to expose, integrate in METS export? (Extraction via JHOVE possible).


[[Category:Virtueller Raum Reichsrecht|Metadata]]
[[Category:Virtueller Raum Reichsrecht|Metadata]]
[[Category:Metadata]]
[[Category:Metadata]]

Latest revision as of 12:35, 17 May 2010

Virr Medium Multivolume 31 Static.gif Virtueller Raum Reichsrecht

Overview
Functionalities
Support
Copyright and Disclaimer
Scope

Metadata:
Application Profile · Content Models
Metadata Display · ViRR Metadata
Action Matrix

Transformations:
virr 2 mets · mab 2 mods
mods 2 oai dc · mods 2 marc21

Specification

Intern:
Meetings · GUI · Miscellaneous
Development · Planning · Feedback
Related Projects:
Judicial Journals · Late Scholasticism
Digitization Lifecycle

edit


Bibliographic Metadata[edit]

Describe the intellectual content of the whole work

The bibliographic data of the digitized works is delivered by the institute in MAB2 ("Maschinenlesbares Austauschformat für Bibliotheken") format. MAB is a special data structure which is used in libraries for the exchange of metadata. For detailed information about the import of MAB data check the corresponding mapping.

Structural Metadata[edit]

Represents the inherent structure of the complete work

Structural Metadata in the context of the ViRR application describe the logical structure of a work.

  • Reflects the division of the work into its constituent parts
  • Depends on the physical carrier medium
  • Special case: An article begins in one work and continues in a second work (one structural element split in two works)

Further understandings of structural metadata which might be addressed at a later stage:

  • Physical structure:
    • Reflects the layout/arrangement of the text on a specific physical artefact
    • Might differ for different physical carrier mediums of the same (intellectual) work
  • Other structural information
    • Dependent on the mark-up language of the transcription (e.g. TEI), other information about the text can be attached, e.g. semantic or syntactic information, incl. linguistic categorizations (clause, morpheme, part-of-speech) or narrative structure (e.g. theme). See TEI-Levels of Transcription.


List of structural element types[edit]

Based on the requirements of the institute, gathered from Goobi and DFG Viewer.

Basic Enhanced Journalproject
* Abschnitt (section)
* Beilage (supplement)
* Corrigenda (corrigendum)
* Danksagung (acknowledgments)
* Einband (cover)
* Einleitung (introduction)
* Errata (errata)
* Faltblatt (leaflet)
* Gesetz (law)
* Illustration (illustration)
* Impressum (imprint)
* Index (index)  
* Inhaltsverzeichnis (table of contents)
* Kapitel (chapter)
* Leere Seite (empty page)
* Nachsatz (trailer record)
* Portrait (portrait)
* Titelblatt (title page)
* Vorwort (preface)
* Widmung (dedication )

* Abkürzungsverzeichnis (list of abbreviations)
* Addenda (addenda)
* Anhang (appendix)
* Ankündigung (announcement)
* Anmerkungen (annotations)
* Anrede (address)
* Artikel (article)
* Aufsatz (essay)
* Autorenindex (index of authors)
* Beitrag (contribution)
* Besitznachweis (proof of ownership)
* Bibliographie (bibliography)
* Brief (letter)
* Chronologischer Index (chronological index)
* Eintrag (entry)
* Gedicht (poetry)
* Handschriftliche Notizen (handwritten notes)
* Illustrationsbeschreibung (illustration description)
* Illustrationsverzeichnis (index of illustrations)
* Interpretation (interpretation)
* Karte (map)
* Kolophon (colophon)
* Komposition (composition)
* Lebenslauf (curriculum vita)
* Literaturverzeichnis (references)
* Nachruf (obituary) 
* Ortsverzeichnis (index of places)
* Ortsplan (city map)
* Personenverzeichnis (index of persons)
* Rechtsprechung (judicature)
* Rezension (review)
* Statistik (statistic)
* Stempel (stamp)
* Tabelle (table)
* Tabellenbeschreibung (table description)
* Tabellenverzeichnis (index of tables)
* Themenindex (index of themes)
* Titelkupfer (frontispiece)
* Verlagsanzeige (publisher's advert)
* Vorsatz (fly-leaf)
* Vortitelblatt (pre-title page)
* Werbung (advertisement)
* Zwischentitelblatt (title page in-between) 
* Sammelrezension (Collective review )
* Miszelle (Miscellany)
* Gesetzgebung (Legislation)
* Sonstiges (Other)

Descriptive Metadata[edit]

Describe the intellectual content of the structural elements of a work

Label (according to ViRR Application Profile) Description MODS Remarks
Title Title <titleInfo> <title>
Numeration Numeration <titleInfo> <partNumber>
Subtitle Subtitle <titleInfo> <subtitle>
Creator (normed) Normed name <name type="personal" authority="pnd"> <namePart> Perhaps in a further step, the creator can be based on an authority file.
Creator (inverted) Inverted name <name type="personal"> <namePart>
Creator display form Display form <name type="personal"> <displayForm>
Creator Role Creator Role <role> <roleTerm type="code" authority="marcrelator"> see roles list under ViRR Application Profile: Creator
Subject Keyword <subject> <topic>
Place Place <originInfo> <place> <placeTerm type="text">
Law Type Law type <subject> <genre> see law types list under ViRR Application Profile: Law Type
Legislature (display) Legislature display form <subject> <name type="corporate"> <display form>
Legislature (origin) Legislature <subject> <name>
Date issued Date issued <originInfo> <dateIssued>
Genre Genre <genre> see list of structural element types
-- Start page Can be captured from the data of the editing interface (after pagination and assigning of pages to structural elements)
-- End page Can be captured from the data of the editing interface (after pagination and assigning of pages to structural elements)
Note Comment <note> e.g. link to external resource
Related Item Continuation <relatedItem> a relation to a structural element within ViRR

Administrative Metadata[edit]

"Information necessary to allow a repository to manage the object: this can include information on how it was scanned, its storage format etc (often called technical metadata), copyright and licensing information, and information necessary for the long-term preservation of the digital objects (preservation metadata)" from Metadata in the Oxford Digital Library.

  • Human readable Copyright & License are described here.
  • Machine readable Copyright & License should be integrated into the ViRR application profile (MODS:copyInformation, accessCondition).
  • Technical Metadata, how to expose, integrate in METS export? (Extraction via JHOVE possible).