-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change resource status to CURATED at the first Publish #47
Comments
In this case I would simply set the status curated every time you publish. It should be a harmless call to the platform right? |
yes although I would actually say only the FIRST time one publishes. seems to be a lot of unnecessary additional calls after that. I am not sure what Unpublish does (do they always (un)publish ALL the curated data or just the data in the active chapter? Since the options appear in the chapter section one assumes they apply only to that chapter) but it could then reset status to ANNOTATED if deleting ALL the curated data (althiugh that seems a bit dangerous since one could always accidentally hit it) |
I really don't want to keep track of an extra thing if it's not necessary. It only adds another silly field to the ET database. Also publishing is not something that happens a lot. Only when you press that button, so it's exactly a wave of HTTP requests the platform has to endure. Also it's actually good to always set it to CURATED, since it might be possible that some other process sets the status on the platform to something else again. In those cases you would want the status to be always set to CURATED in any case. Also the publish is for the entire mediaresource. The button is in a not so handy place, I admit. It should be moved somewhere at the top. Also unpublish removes all the curated RDF triples from the platform. (so publish is only needed to add triples to the store and set the status to CURATED) |
ok, agree: publish: change status to CURATED. unpublish: change status to ANNOTATED. |
@jthomsen "yes. the first "Publish" would be the best imho; Jaap could do this via a REST call, just as Pieter sets the status to TRANSFERRED as soon as it is transferred and encoded"
The text was updated successfully, but these errors were encountered: