There is no such content in this group
Posts
28
February
2017
Notes from 28-Feb-2017 Meeting; Next call 14 March 14:00 UTC
It was a small group today, just myself, Frederik and Ulrich. We discussed Thomas' Reptor implementation. Frederik suggests that maybe one approach to addressing the complexity issue would be to make it required for server implementations to explicitly declare the default values for the required elements of the schema. Since the default values should represent the lowest common denominator behavior, it should mean minimal burden on the server implementation and enable clients to have a4 | Add new comment
28
February
2017
Reminder: Call today at 14:00 UTC
Hi all, Just a reminder that we have our semi-monthly call today. Hope to talk to most of you soon! Notes from last meeting are here: https://www.rd-alliance.org/group/research-data-collections-wg/post/note... Bridget0 | Add new comment
27
February
2017
Implementation of the API in Reptor
Dear all, I'm working already for some time on a repository software which implements some of the RDA recommendations (DFT, DTR etc.). So I moved the "standalone" implementation of the API I did so far into the "Reptor" software. I installed an empty instance of Reptor for playing around with the collection API. Feel free to kill it :-) : http://reptor.thomas-zastrow.de/col-wg/index.php -> There is an example folder "photos" which shows most of the4 | Add new comment
15
February
2017
Authentication problem
Dear all, In the API, we have read and write calls to the same endpoint. For example: /collections/{id}/members/ When sending a GET request, it means "Get the members in that collection". If sending a POST, it means "Add a new member to this collection". When having only one endpoint for both kind of operations, any differentiation between read/write calls has to be done *on the application level*. In other words, it has to be *implemented* in the instance of the collection API. It is no longer possible to just put4 | Add new comment
14
February
2017
Simple Python client
Dear all, We talked about clients accessing the collection API - I wrote a short Python script which uses only the two functions "Give me all collections" and "Give me all members of a collection" to create a (recursive) graph out of the content of a collectors API instance in Dot language. Visualized with GraphViz, the graph looks like this: https://github.com/TomZastrow/collection-api/blob/master/graph.png Here is the Python script:3 | Add new comment
14
February
2017
Notes from 14-Febuary Call
Next calls: Feb 28, March 14 & 18, 14:00 UTC Action Items for the next month: * Frederik, Alex and Thomas to continue working on implementations o All three need to be put into the GitHub collections organization so that we can point adopters there (https://github.com/RDACollectionsWG/) * Bridget, Tobias and Maggie (and anyone else who wants to) will write up technical details of how we each intend to adopt the API for our0 | Add new comment
14
February
2017
Fwd: YACA - Yet another collection API
-------- Weitergeleitete Nachricht -------- Betreff: YACA - Yet another collection API Datum: Thu, 2 Feb 2017 15:03:18 +0100 Von: Thomas Zastrow <***@***.***> An: Tobias Weigel <***@***.***>, Baumgardt, Frederik <***@***.***>, Almas, Bridget M. <***@***.***> Following the CRUD approach, this would be: - List all existing collections - Create a collection - Read a collection (returning all items it contains) - Add an item to a collection - Delete an item from a collection0 | Add new comment
14
February
2017
Reminder: Web Conference Tuesday 14 Feb 14:00 UTC (9am EST/3pm CET)
Dear all, Just a reminder that we have our regular GoToMeeting video call at 3pm CET / 9am EST on Tuesday 14 Feb. The technical details are at www.rd-alliance.org/group/research-data-collections-wg/event/research-da... Best, Bridget0 | Add new comment
31
January
2017
Minutes from today meeting
- Alex made some progress on the demonstrator. Alex will get the demonstrator nearly done in the next month - Alternative implementation from Frederik, can share some code with Alex implementation - Both implementations will have different backends (Redis, Triple Store) - - maxDepth: - default will be 0 - maxDepth: will be property on the service level - appendsToEnd: is the collection a stack or a queue - it is possible to add an element at any place in the list (adding in the middle)1 | Add new comment
31
January
2017
Regular Collections WG video call today at 14:00 UTC
Dear all, Today is the last Tuesday of the month and we will have a GoToMeeting video call at 3pm CET / 9am EST. The technical details are here: https://www.rd-alliance.org/group/research-data-collections-wg/event/res... Today’s agenda items are: 1. Discussing plans for the demonstrator 2. Input on the maxDepth property 3. Discussing item mapping functions Hope to see you in the call, Frederik —0 | Add new comment