-
Notifications
You must be signed in to change notification settings - Fork 18
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
Update README.md #583
Update README.md #583
Conversation
To the list of changes that the SPA introduces, this adds that Dataverses are called referred to as collections, instead
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'll let the frontend team approve this but it looks good to me!
One thought is that we could also reword the #### Dataverses/Datasets list
item above to talk about collections instead of dataverses. This could be in a separate PR if we wish.
Also, I'm not sure how this items are ordered but this new one (#### Dataverses are Called Collections
) probably belongs at or at least near the top.
@pdurbin I've implemented your docs suggestions, take a look please and approve it if you think its ok. Thanks! |
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.
Looks good! Approved!
proof-read, merging pr |
What this PR does / why we need it:
To the list of changes that the SPA introduces, this PR adds that Dataverses are referred to as collections, instead.
Which issue(s) this PR closes:
Special notes for your reviewer:
Suggestions on how to test this:
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
This PR doesn't introduce a user interface change
Is there a release notes update needed for this change?:
I don't think a release note is needed for this change.