Deposit Workflow:
The framework has identified the point of deposit of an object into a repository as a crucial stage in version identification.
It is the easiest opportunity for communication to take place between the depositor and the repository about what version is being deposited. If version information is captured at this time, from the most reliable source on the matter (usually the content creator) then the repository can store accurate information immediately.
Duplication is also a significant problem in version identification, where multiple similar versions are deposited in a single repository or found across multiple repositories, with no information about which one is which or how they are related.
Deposit processes need to be able to capture version information, automatically if possible, at deposit, and to also assist the depositor in avoiding duplication for future ambiguity over what versions they've made available by automatically searching:
- The local repository for possible other versions of the object and if any are found ensuring suitable options for disambiguation (i.e. via linking of versions) takes place
- External repositories for possible other versions of the object to ensure co-authors or related parties haven't deposited different or possibly conflicting objects elsewhere
Next Section:
Please go to the page on Sharing Standards.