EsciDoc Item Origin

When fetching data from an external service it is desirable to store the information where and when this data was fetched. For long term archiving aspects it is desirable to store the original fetched metadata record, as well.

Open: Where to store origin MDMetadata (PREMISPreservation Metadata: Implementation Strategies?) in origin or escidoc item. How to handle the relation when an item is updated?

accepted

Store the fetched data as component of the created escidoc item

Pro: Metadata can be stored in different formats, not only xml

Con: Logic changes needed (invisible component)

Open:

rejected due to item overload

Create additional metadata record where this info is stored

Pro: MDMetadata is stored directly in item

Con: Increasing FoXML size due to versioning

Open: How can we handle fetched components (full texts)?

rejected

Store all data in one item (fetched data is first version, escidoc data second etc.)

Pro: No overhead, Easy retrieval of data.

Con:

Open:

rejected, as there is no clear way how to match always to version 1

I would actually mostly vote for one of two alternatives: additional metadata record or additional component; where additional metadata record is logically better approach; However, here we have technical issues with large FoXMLs and visioning. Therefore, probably more pragmatical approach would be to store it as a component with special content category. The content of this component should be XMLExtensible Markup Language i.e. a Premis metadata record that provides information on the original identifier, original repository, time of creation etc. this could be more detailed including the metadata on rights, etc. see Ulla's remark below. --Natasa 15:08, 26 February 2009 (UTCCoordinated Universal Time)

Why we want to store origin information

Different visualization on GUIGraphical User Interface for imported items?

Source depended rights handling

Maintenance issues (richer transformation after mapping rework)

Misc

Do we handle Metadata and full texts differently?

In case fetched data are transformed a) into escidoc items and/or b) into other format (e.g. part of authoring tools), the idea of storing original data related to escidoc data sounds good to me. In any case, information on date and source should be kept, just in case we have to legitimate the quality of fetched data. In addition, we might get confronted with rights information related to the source, which has to be stored as well (e.g. constraints for re-use by source, or indication of ownership)--Ulla 13:37, 26 February 2009 (UTCCoordinated Universal Time)