[
https://jira.duraspace.org/browse/DS-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20677#action_20677
]
Robin Taylor commented on DS-923:
---------------------------------
I suspect I am talking crap here (not unusual). I guess there is no issue in
using the internal id's in URLs here since they are not meant to be persistent
URLs ?
Apologies for thinking this through in a Jira issue.
> 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 contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
