Hi again, Is it possible that the behavior of /handle is different from that of /items in the sense that when I change metadata from xmlui I see the change immediately with /items but not with /handle.
I've tried changing a title of an item https://demo.dspace.org/rest/handle/10673/26?expand=metadata here I still see the old title: <metadata> <key>dc.title</key> <language>en_US</language> <value>TEST2</value> </metadata> but if I check https://demo.dspace.org/rest/items/19?expand=metadata which should be the same item, i see the updated one <metadata> <key>dc.title</key> <language>en_US</language> <value>TEST2 Title</value> </metadata> The same goes for the name field. Is there some different caching for /handle? OK 2015-07-28 13:32 GMT+02:00 Ondřej Košarko <kosa...@ufal.mff.cuni.cz>: > Hi Peter, > thanks for your reply and thanks again for posting the example with the > ?expand parameter; I completely missed that part in to documentation. > > Regards, > OK > > 2015-07-27 19:12 GMT+02:00 Peter Dietz <pe...@longsight.com>: > >> Hi OK, >> >> I've updated the documentation to mention the /handle/{prefix}/{suffix} >> endpoint: >> https://wiki.duraspace.org/display/DSDOC5x/REST+API#RESTAPI-Handle >> >> ________________ >> Peter Dietz >> Longsight >> www.longsight.com >> pe...@longsight.com >> p: 740-599-5005 x809 >> >> On Mon, Jul 27, 2015 at 12:37 PM, Peter Dietz <pe...@longsight.com> >> wrote: >> >>> Hi OK, >>> >>> The endpoint to look up an object by its handle is >>> <base-rest-url>/handle/<handle-number>. So, for example: >>> https://demo.dspace.org/rest/handle/10673/14?expand=all >>> >>> The /handle/<handle-number> endpoint doesn't appear to be properly >>> documented. Here is the HandleResource in the code. >>> >>> https://github.com/DSpace/DSpace/blob/master/dspace-rest/src/main/java/org/dspace/rest/HandleResource.java#L37 >>> >>> It produces a rest DSpaceObject (so if the handle yields an Item, the >>> response is a rest Item in json/xml). >>> { >>> id: 10 >>> name: "Test submit" >>> handle: "10673/14" >>> type: "item" >>> link: "/rest/items/10" >>> expand: >>> [ >>> 0] >>> lastModified: "2015-07-27 11:00:18.027" >>> ... >>> >>> ________________ >>> Peter Dietz >>> Longsight >>> www.longsight.com >>> pe...@longsight.com >>> p: 740-599-5005 x809 >>> >>> On Fri, Jul 24, 2015 at 6:54 AM, Ondřej Košarko < >>> kosa...@ufal.mff.cuni.cz> wrote: >>> >>>> Hi all, >>>> >>>> Is it currently possible, using the dspace5 rest api, to access the >>>> items/collections/communities using handles rather than internal-ids? >>>> >>>> I can see a workaround for items - first find-by-metadata-field. But >>>> that seems bit cumbersome. Handles or some other PIDs are already used to >>>> reference items*, collections, etc. and they are "guaranteed" not to >>>> change. >>>> >>>> *imagine you want to have on your personal homepage, together with PID, >>>> some other metadata for the submission. >>>> imagine you are using dc.relation.* (with PIDs as value) to link some >>>> of the submissions together and are creating a visualization of the >>>> relations. >>>> >>>> It's doable for items but there always will be at least two requests >>>> for each, or am I missing some other way? >>>> >>>> Regards, >>>> OK >>>> >>>> >>>> PS: Is it possible to have wildcards in metadataEntries? Both - keys >>>> and values? >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> DSpace-tech mailing list >>>> DSpace-tech@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech >>>> List Etiquette: >>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette >>>> >>> >>> >> >
------------------------------------------------------------------------------
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
