-
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
create links key at node level in registry #17
Conversation
README.md
Outdated
| `cite-as` <br> `publication` | Attribution by researchers to reference the node when using it for publications | | | ||
| `copyright` <br> `license` <br> `terms-of-service` | Legal use of the node | | | ||
| `describedby` | URL to full documentation and details of the node, its purpose and so on | | | ||
| `edit` | A self-reference to https://github.com/DACCS-Climate/DACCS-node-registry or anywhere that the specific node registry entry to redirect users where to update it | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I follow the wording of this entry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'll do a little proofread/edit and make the wording a bit more consistent
node_registry.json
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need the node_registry.json
file in this branch anymore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes we do. The node_registry.json
in this file contains the static information and should be edited by node managers. The version in the current-registry branch has a superset of that info that includes all the data grabbed daily from the node endpoints and some additional metadata.
As suggested in #10, this does the following:
links
key for each nodeurl
key with an entry inlinks
(rel
=service
)icon_url
key with an entry inlinks
(rel
=icon
)rel
=version
entry inlinks
(refers to the/version
endpoint)rel
=collection
entry inlinks
(refers the the/services
endpoint)Resolves #10