Documentation: Align Chullo with Fedora API Spec

Created on 30 Mar 2017 · 7Comments · Source: Islandora/documentation

Now that we're dusting off Chullo, we should do some gardening to put it in alignment with the Fedora API specs being worked on. Though they are still works in progress, there are some things that are definitely going to happen and we should account for them.

[x] Remove COPY
[x] Remove MOVE
[x] Rebrand transactions as atomic operations
[x] Remove UUID utilities

chullo

Source

dannylamb

All 7 comments

Couple questions, should we just alter our COPY to be a PUT of an existing resource and alter our MOVE as a PUT and a DELETE (keeping in mind @acoburn's points from the CLAW call)?

whikloj on 30 Mar 2017

👍1

@whikloj the question, I think, is whether the goal of Chullo is to be a "generic Fedora client" or whether it will introduce extra semantics. If the latter, then there is nothing wrong with adding extra features (e.g. COPY, MOVE), but if I were designing it, I'd leave those for some "higher-level client"; that is, make Chullo a generic Fedora client (and nothing more), and leave these other operations to some other layer in the stack.

acoburn on 30 Mar 2017

👍1

In the very least they should be removed from the FedoraAPI interface and implementation. I'm inclined to ditch those operations entirely and stick to spec, but it's certainly open for discussion.

dannylamb on 30 Mar 2017

Rebrand transactions as atomic operations

At this point in time, Atomic Batch Operations are not apart of the Fedora API Specification. It is a separate specification that a given implementation may or may not support. So, I would also remove that from Chullo as well. Especially, if we're going to make Chullo a generic Fedora client as @acoburn suggests.