[
https://jira.duraspace.org/browse/DS-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Taylor closed DS-923.
---------------------------
Resolution: Won't Fix
Just a lack of understanding on my part.
Cheers, Robin.
> REST-API Currently exposes and uses the internal DSpace database object id.
> ---------------------------------------------------------------------------
>
> Key: DS-923
> URL: https://jira.duraspace.org/browse/DS-923
> Project: DSpace
> Issue Type: Bug
> Components: REST API (experimental)
> Reporter: Robin Taylor
>
> The internal database id's are currently exposed in responses to the REST API
> eg <id type="number">58</id>
> In fact the internal id appended to the URL to limit the query to one object
> http://localhost:8080/rest/items/58.xml
> Should we be exposing internal id's or should we only be using handles ? My
> knee jerk reaction says handles but that would preclude exposing items which
> are still in submission or workflow and therefore do not yet have a handle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
