[
https://jira.duraspace.org/browse/DS-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27672#comment-27672
]
Mark H. Wood commented on DS-220:
---------------------------------
IdentifierProviders are pluggable now. There might not *be* a handle/item_id,
*ever*. DOIs might be all that a site uses. (That's going to have
implications all over.)
What happens if we coin a locally-unique ID, in cases where we can't or won't
give a globally-unique ID because the submission is not complete? If we do,
then we should provide some way for submitters to later associate the completed
submission with "final" IDs issued later, by looking up the "preliminary" ID.
Probably the ordinary harvesting or REST channels could be used to discover
additional UIDs.
What do other systems do? DSpace can't be the only software with blocking
states in its workflows.
> No unique identifier returned in the SWORD response for the deposit if a
> workflow is configured for the collection
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DS-220
> URL: https://jira.duraspace.org/browse/DS-220
> Project: DSpace
> Issue Type: Bug
> Components: SWORD
> Affects Versions: 1.5.2
> Environment: Collection is configured to require a accept/reject
> process. Doing a deposit using a SWORD client. The deposit is successful but
> no unique id is returned in the SWORD response.
> Reporter: Andrew Bai
> Assignee: Mark H. Wood
> Priority: Major
> Attachments: deposit_response_rmpl_withioutworkflow.xml,
> deposit_response_rmpl_withworkflow.xml
>
>
> in the response returned from the deposit, the "atom entry" doesn't have a
> unique id. Instead it just has the following url that points to the homepage
> of the DSpace JSP user interface: http://vm:12:8080/jspui. It also doesn't
> have a "atom:content" entry which is required according to SWORD profile 1.3.
> In SWORD AtomPub profile version 1.3, the following extracts can be found in
> section 9.6:
> "the atom:id element MUST contain a unique identifier for the deposit";
> "MUST contain an atom:content element with a src attribute containing a uri"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
