search

coar-notify / coar-notify.net

Sources for the COAR Notify website
Creative Commons Attribution 4.0 International
4 stars 1 forks source link

Document PreReview workflow #5

Closed paulwalk closed 3 months ago

paulwalk commented 4 months ago

Have asked Sean Wiseman for an example notification

paulwalk commented 3 months ago

Have asked Sean to review this for us.

This is what I said to him:

... https://notify.coar-repositories.org/catalogue/workflows/repository-prereview-1/ You will see that I have made a change to the payload in that the Activity ID is a urn:uuid. In your example, the Activity ID repeats the Object ID (a DOI in HTTP form in this case). While an HTTP URI is valid for the Activity ID, I think using the Object ID is confusing. The protocol says:

"Notify payloads must describe an AS 2.0 activity. The activity has an id which must be a URI, and the use of URN:UUID is recommended. An HTTP URI may be used instead, but in such cases the URI should resolve to a useful resource."

which is, perhaps, also a little unclear.

Do you have nay thought on this? I think having two completely different things in the payload have the same ID is not optimal...

paulwalk commented 3 months ago

Sean agrees and is talking to Ted (?) from BioArxiv about correcting this. In the meantime, I have published the documented workflow here:

https://notify.coar-repositories.org/catalogue/workflows/repository-prereview-1/