Difference between revisions of "Talk:ESciDoc Services DataAcquisitionHandler"
Jump to navigation
Jump to search
Kleinfercher (talk | contribs) m (→Approaches) |
m (typos) |
||
| Line 8: | Line 8: | ||
When fetching data from an external service it is desirable to store the information where this data was fetched. | When fetching data from an external service it is desirable to store the information where this data was fetched. | ||
===Approaches=== | ===Approaches=== | ||
# Create additional attribute for | # 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 own item and somehow relate the corresponding(transformed) escidoc item | ||
# Store the fetched data as component of the created escidoc item | # Store the fetched data as component of the created escidoc item | ||
Revision as of 14:45, 23 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)
- 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.