Skip to content
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

DD3 R1 Introduce GEMINI in the context of wider principles #31

Closed
PeterParslow opened this issue Apr 7, 2021 · 5 comments
Closed

DD3 R1 Introduce GEMINI in the context of wider principles #31

PeterParslow opened this issue Apr 7, 2021 · 5 comments
Labels
DD3 Recommendation from the Geospatial Commission Data Discoverability 3 project documentation Improvements or additions to documentation

Comments

@PeterParslow
Copy link
Contributor

This recommendation arose from Peer Review comments while drafting this document. That is, some of the peer review organisations feel that GEMINI should promote itself more, in the context of things like the UK National Data Strategy.
GEMINI supports several aspects of good data management, such as making it easier to find and access the data. At the moment, these are framed in the National Data Strategy and Location Data Strategy. The GEMINI introductory pages should make more of this relationship in order to make it clearer how an organisation can benefit from adopting GEMINI.
It would also be useful to link to the UK government guidance that recommends public authorities to use GEMINI, and to provide links to related resources such as GEMINI software implementations.

@PeterParslow PeterParslow added documentation Improvements or additions to documentation DD3 Recommendation from the Geospatial Commission Data Discoverability 3 project labels Apr 7, 2021
@PeterParslow
Copy link
Contributor Author

There are also general recommendations from the "Data Discoverability" projects about writing this page in a more user friendly way. Here is a revised word document, with the small change from #24 and more extensive changes related to this issue.
1037-uk-gemini-standard 2-3 revised for issue 2020-02 and DD3 R1.docx

@PeterParslow PeterParslow added this to For review in GEMINI issue handling May 21, 2021
@PeterParslow PeterParslow moved this from For review to Pending release in GEMINI issue handling Jun 2, 2021
@PeterParslow
Copy link
Contributor Author

2021-06-08: inconsistent between "UK GEMINI" and "GEMINI". Go for "UK GEMINI" on first use, but introduce "(also known as GEMINI)". Change occurrence in third paragraph to just "GEMINI".

Should first spell out the acronym.

Move the GDS recommendation sentence into the first paragraph, as second sentence.

See also #58.

@PeterParslow
Copy link
Contributor Author

Emailed to Blue Star (AGI web support)

@PeterParslow PeterParslow moved this from Pending release to For closure in GEMINI issue handling Jun 29, 2021
@PeterParslow PeterParslow moved this from For closure to With AGI to publish in GEMINI issue handling Jul 13, 2021
@PeterParslow
Copy link
Contributor Author

Note: this issue has not (yet) been included in the text migrated to GitHub. I will therefore move it "back" from "With AGI to publish" to "Pending release". Same applies to #58.

#24 has been implemented (on GitHub)

@PeterParslow PeterParslow moved this from With AGI to publish to Pending release in GEMINI issue handling Mar 16, 2023
@PeterParslow PeterParslow moved this from Pending release to PR raised for Dev in GEMINI issue handling Oct 5, 2023
@archaeogeek archaeogeek moved this from PR raised for Dev to PR merged to Dev in GEMINI issue handling Nov 1, 2023
@archaeogeek
Copy link
Member

Closed- @archaeogeek to get link on main AGI website changed to new intro page

@archaeogeek archaeogeek removed this from PR merged to Dev in GEMINI issue handling Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DD3 Recommendation from the Geospatial Commission Data Discoverability 3 project documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants