Thanks Don.

Fixed in the 3.6 docs 
(https://wiki.duraspace.org/display/FEDORA36/REST+API#RESTAPI-getDatastreamHistory)

There was a point in development where it was /versions but we ultimately 
settled on /history and the docs must not have followed, viz. 
https://jira.duraspace.org/browse/FCREPO-675

On Mar 9, 2013, at 5:03 AM, Donald Brower <[email protected]> wrote:

> The online docs for Fedora 3.6 say the path for the API-M method
> getDatastreamHistory is
> 
> /objects/{pid}/datastreams/{dsid}/versions ? [format]
> 
> 
> 
> But, from playing with a local copy of Fedora, it seems the path is really
> 
> /objects/{pid}/datastreams/{dsid}/history ? [format]
> 
> 
> 
> I think this is just a mistake in the documentation.
> 
> 
> -Don
> 
> 
> --
> Donald Brower, Ph.D.
> Digital Library Infrastructure Lead
> Hesburgh Libraries, University of Notre Dame
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
> endpoint security space. For insight on selecting the right partner to 
> tackle endpoint security challenges, access the full report. 
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> Fedora-commons-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers


------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Fedora-commons-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers

Reply via email to