EUDAT-B2SHARE
Allow community administrators to list and read user drafts
Why do they need this? Is it not just the "review" UI page which is missing? Then we can allow again the review_and_publish workflow.
A community application (a b2share client) lists, reads, and updates the community drafts in order to automatize certain tasks (e.g. input of metadata). Furthermore, this allows community specific logic to be separated from the service itself (since the api is out there).
Later on, a community admin (a person) reviews the pre-processed draft (e.g. through the draft /edit link) and publishes it.
@janiheikkinen Thank you for the clarification.
We already have some review mechanism implemented but not yet accessible in v2. Could you tell me if the following would fit your needs:
B2SHARE current workflow can be summarized as: a user submits a draft record and then publishes it. B2SHARE has internal support for another workflow which can be summarized as:
- a user submits a draft record. The record "publication_state" field is "submitted".
- community administrators can review draft records in "submitted" state, and then publish it, or put it back in "draft" state if it is refused.
The only reason why we didn't integrate this workflow in V2.0.0 is that we don't have yet the UI for reviewing records.
It would be possible to:
- create a REST API token for community administrators and use it for your automatic tasks
- the automatic tasks would update fields inside the record to say when they are valid.
- community admins could then filter submitted draft records based on the validation.
It is the latter workflow that very likely fits the community needs. However, there might be a need for additional publication_state value, e.g. 'preprocessed'. Currently, already preprocessed drafts are filtered out by comparing the 'created' and 'updated' timestamps.
The only reason why we didn't integrate this workflow in V2.0.0 is that we don't have yet the UI for reviewing records.
Would it be feasible to allow access the drafts through the /edit (instead of review UI) link assuming the community admins have permission to list and read all the community drafts?
@janiheikkinen Thanks for your feedback. Reusing the /edit would possible but this will be decided when we design the feature after gathering more requirements. For now we can't yet say what it will look like.
We will keep in mind that there is a need for:
- drafts having one or more steps of preprocessing.
- filtering drafts based on the preprocessing stage.
- enabling community administrators to edit the drafts before publishing.
Don't hesitate to correct me if this doesn't summarize your requirements.