[
https://jira.duraspace.org/browse/DS-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20684#action_20684
]
Tim Donohue commented on DS-923:
--------------------------------
Robin,
Yea, I'm not sure this is that big of a deal. Again, it's following REST URL
Conventions, which by nature expose internal IDs of objects:
http://microformats.org/wiki/rest/urls
So, I don't see a real concern about exposing DSpace internal IDs via REST.
However, we may want to ensure there is a way to use a Handle to lookup the
Internal ID (or similar). I'm not sure that this is possible yet in the REST
API, but it seems logical that someone should be able to retrieve an object via
its Handle as well.
Perhaps something like:
GET /resource/{handle}
Which could essentially just perform some sort of Handle lookup, and redirect
you to a path like:
GET /items/{ID}
or
GET /collections/{ID}
(etc.)
Not sure if this gets more to your point here (or if I've hijacked your JIRA
issue a bit). In any case, I don't think there's a problem with exposing
internal IDs via REST. But, we should also provide a way via REST to access
objects via their Handles. This would allow an alternative way to access an
object, if you are unsure of the actual internal ID (or if the internal ID has
actually changed, because the object was re-imported or moved from one DSpace
to another).
> 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
