Difference between revisions of "PubMan Duplicates"
Jump to navigation
Jump to search
(links to edoc) |
m (categorized page) |
||
| Line 25: | Line 25: | ||
*# a new intellectual version should be created for the target item | *# a new intellectual version should be created for the target item | ||
[[Category: | [[Category:PubMan_Functional_Specification|Duplicates]] | ||
Revision as of 18:59, 17 April 2009
The PubMan solution should provide reasonable mechanism for detecting and handling duplicates. This page should collect related use cases.
Duplicate Detection[edit]
Question: How to identify duplicates?
Status on eDoc[edit]
- two items are considered as duplicates if they have an identifier of the same type with identical value
- the duplicate check is triggered when
- items are copied from virtual collection to archival collection (batch)
- one item is copied from one virtual or archival collection to another archival collection (manual)
- the duplicate check is not triggered when
- items are moved from one archival collection to another one (batch)
EndNote[edit]
- offers an action "Find duplicates" via its References menu
- action can be setup via user preferences where the user can change which set of fields should be considered for the detection and if the "spaces and punctation should be ignored"
Duplicate Handling[edit]
How to proceed if duplicates have been detected?
Status on eDoc[edit]
- if two items are considered as duplicates, the system asks the user if
- the process should be canceled
- a new metadata version should be created for the target item
- a new intellectual version should be created for the target item