Talk:ESciDoc Services DataAcquisitionHandler
Integrate SWORD?[edit]
SWORD is a profile of the Atom Publishing Protocol and a lightweight protocol for deposit.
- Exposing and importing data
- Depositing supported by arxiv. (Probably nice feature to enable export to arxiv when creating an item in pubman)
experiences in using SWORD for Facebook=> repository (ePrints) can be found | here. In any case, if scenarios for automatic submission to discipline-specific repositories could be supported, of great value within MPG...but still have not understood how different privileges and workflows are solved. --Ulla 12:52, 26 February 2009 (UTC)
- How is this topic related to the syndication manager?
How to Store the Origin Information of an Item[edit]
When fetching data from an external service it is desirable to store the information where this data was fetched.
Approaches[edit]
- Create additional attribute for an Identifier (this one could even be invisible for the user)
- Store the fetched data as own item and somehow relate the corresponding(transformed) escidoc item
- Store the fetched data as component of the created escidoc item
- Create additional metadata field where this info is stored
- Create additional metadata record where this info is stored
- 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 versioning. Therefore, probably more pragmatical approach would be to stor it as a component with special content category. The content of this component should be XML i.e. a Premis metadata record that provides information on the original identifier, original repository, time of creation etc this could be more detailed inlcuding the metadata on rights, etc. see Ulla's remark below. --Natasa 15:08, 26 February 2009 (UTC)
Misc[edit]
- Do we want to store the date of fetching as well? If yes, where?
- Original MD record has to be stored for ICE.
- 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 (UTC)