Difference between revisions of "Talk:ESciDoc Services DataAcquisitionHandler"
Jump to navigation
Jump to search
m (typos) |
(→Integrate SWORD?: added link to to sword) |
||
| Line 3: | Line 3: | ||
*Exposing and importing data | *Exposing and importing data | ||
*Depositing supported by [http://arxiv.org/help/submit_sword arxiv]. (Probably nice feature to enable export to arxiv when creating an item in pubman) | *Depositing supported by [http://arxiv.org/help/submit_sword 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 [http://learninglab.lincoln.ac.uk/blogs/joss/2008/12/17/facebook-to-the-repository-via-sword/ | 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. --[[User:Uat|Ulla]] 12:52, 26 February 2009 (UTC) | |||
*How is this topic related to the syndication manager? | *How is this topic related to the syndication manager? | ||
Revision as of 12:52, 26 February 2009
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
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.