Differences between revisions 1 and 2
Revision 1 as of 2008-06-26 12:26:04
Size: 2161
Editor: kfc
Comment: Created by the PackagePages action.
Revision 2 as of 2010-03-17 13:12:49
Size: 2283
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
''This document was imported from'': [http://hera/cgi-bin/viewcvs.cgi/*checkout*/DOMS/Ingest/design/contentsDescription.tex?rev=HEAD contentsDescription.tex] ''This document was imported from'': [[http://hera/cgi-bin/viewcvs.cgi/*checkout*/DOMS/Ingest/design/contentsDescription.tex?rev=HEAD|contentsDescription.tex]]
Line 5: Line 5:
''Author'': [:bam: bam] ''Author'': [[bam]]
Line 11: Line 11:
[#fig1 fig. 1]. The PID of an object is [[#fig1|fig. 1]]. The PID of an object is
Line 23: Line 23:
[:SB_DOMS_object_structure:]. [[SB DOMS object structure]].
Line 25: Line 25:
[[Anchor(fig1)]]
attachment:SB_types.png
<<Anchor(fig1)>>
{{attachment:SB_types.png}}
Line 32: Line 32:
summarised in figures [#fig2 2], [#fig3 3],
[#fig4 4], [#fig5 5], [#fig6 6],
[#fig7 7], [#fig8 8] and [#fig9 9].
summarised in figures [[#fig2|2]], [[#fig3|3]],
[[#fig4|4]], [[#fig5|5]], [[#fig6|6]],
[[#fig7|7]], [[#fig8|8]] and [[#fig9|9]].
Line 40: Line 40:
[[Anchor(fig2)]]
attachment:Type_type.png
<<Anchor(fig2)>>
{{attachment:Type_type.png}}
Line 47: Line 47:
[[Anchor(fig3)]]
attachment:Type_rights.png
<<Anchor(fig3)>>
{{attachment:Type_rights.png}}
Line 54: Line 54:
[[Anchor(fig4)]]
attachment:Type_non-project.png
<<Anchor(fig4)>>
{{attachment:Type_non-project.png}}
Line 61: Line 61:
[[Anchor(fig5)]]
attachment:Type_file.png
<<Anchor(fig5)>>
{{attachment:Type_file.png}}
Line 68: Line 68:
[[Anchor(fig5)]]
attachment:Type_image.png
<<Anchor(fig5)>>
{{attachment:Type_image.png}}
Line 75: Line 75:
[[Anchor(fig6)]]
attachment:Type_audio.png
<<Anchor(fig6)>>
{{attachment:Type_audio.png}}
Line 82: Line 82:
[[Anchor(fig7)]]
attachment:Type_video.png
<<Anchor(fig7)>>
{{attachment:Type_video.png}}
Line 89: Line 89:
[[Anchor(fig8)]]
attachment:Type_text.png
<<Anchor(fig8)>>
{{attachment:Type_text.png}}
Line 96: Line 96:
[[Anchor(fig9)]]
[[ImageLink(http://merkur/viewvc/trunk/docs/legacy/typeHierarchy.png?root=doms&view=co)]]
<<Anchor(fig9)>>
[[http://merkur/viewvc/trunk/docs/legacy/typeHierarchy.png?root=doms&view=co|{{http://merkur/viewvc/trunk/docs/legacy/typeHierarchy.png?root=doms&view=co}}]]
Line 99: Line 99:
Figure 9. DOMS object type hierarchy. [http://merkur/viewvc/trunk/docs/legacy/typeHierarchy.fig?root=doms&view=co Original xfig source]. Figure 9. DOMS object type hierarchy. [[http://merkur/viewvc/trunk/docs/legacy/typeHierarchy.fig?root=doms&view=co|Original xfig source]].

DOMS Contents Description

This document was imported from: contentsDescription.tex

Author: bam

Object Types

All objects to be ingested in the DOMS must implement the SB type, which is summarised in fig. 1. The PID of an object is 'projectname:objectname', i.e. the left side should be a known project; the right side should be 'project' for a project object and an object name for non-project objects. 'Known' projects should be specified in Fedora properties.

We do not have a final DOMS Dublin Core description (Language? Should format and rights be described in DC as well as in RELS-EXT? We talked about letting the Fedora Dublin Core be a simple 'title-holder' and then introduce an SB Dublin Core datastream. Why was that and should we?); a good suggestion can be found on SB DOMS object structure.

SB_types.png

Figure 1.

All other types of objects are additions to the SB type and are summarised in figures 2, 3, 4, 5, 6, 7, 8 and 9.

We are still missing descriptions of type, rights and technical datastreams. These are necessary to define for the validation iteration

Type_type.png

Figure 2.


Type_rights.png

Figure 3.


Type_non-project.png

Figure 4.


Type_file.png

Figure 5.


Type_image.png

Figure 5.


Type_audio.png

Figure 6.


Type_video.png

Figure 7.


Type_text.png

Figure 8.


http://merkur/viewvc/trunk/docs/legacy/typeHierarchy.png?root=doms&view=co

Figure 9. DOMS object type hierarchy. Original xfig source.


ActionSalvageDataModel/DOMSContentDescription (last edited 2010-03-17 13:12:49 by localhost)