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

Standardize standard pages (ha!) #127

Merged
merged 40 commits into from
Jan 15, 2019
Merged

Standardize standard pages (ha!) #127

merged 40 commits into from
Jan 15, 2019

Conversation

peterdesmet
Copy link
Member

@peterdesmet peterdesmet commented Dec 31, 2018

Each standard page now starts with the same default header section (based in part on the SDS). This section contains a Title, Date created, Status, Category, Permanent IRI, Abstract, (Contributors), Creator, and Bibliographic citation. I have tried my best to populate these for all 25 standards, which worked for most (pending some fields that could be updated by anyone later). For those standards were I could not find any information I have hidden the page and created issues: #121, #123, #124, #125, #126.

Note: I have not updated the README in the repo for these standards (e.g. using the same citation formatting for all bibliographic citations).

Also included:

  • Add summary to all standards
  • Add relevant cover image to all standards
  • Move Darwin Core maintenance group to community

/cc @baskaufs

Is obsolete content that should not have been moved to new website
- Move summary of charter to summary of page
- Don't add maintenance group to title
- Add tags "interest group, "maintenance group"
- Include DOI link in reference, drop title

Ping @tucotuco the becoming involved mentions that people should contact convener or core members, but not contact info is provided. Do we want to include emails (of at least you as convener) and/or suggest another way, e.g. by watching the dwc repo.
- Add summary
- Use abstract from publication
- Use header section
- Reduce other text
@baskaufs
Copy link

baskaufs commented Jan 3, 2019

I have previously put quite a bit of time in tracking down where the documents can be accessed for all of the prior TDWG standards. This information is in the table docs.csv in the docs folder of the rs.tdwg.org repo. The browserRedirectUri column is the URL that will actually take you to the place where the document can be retrieved (if it is retrievable). In several cases, the standards documents are only available in print and in those cases, the URL takes you to a description of the print work. In at least one case (I think it's XDF) the actual standard document itself seems to be lost. The DOI I've listed is actually to a publication about the standard.

I have also tracked down information about all authors of the documents and URIs for those authors (mostly ORCIDs, VIAFs, or Wikidata IDs). The author/doc info is in the table docs-authors.csv.

@baskaufs
Copy link

baskaufs commented Jan 3, 2019

I should have also mentioned that I wrote an abstract for every document. It's possible that you could write a script to generate what you want from the tables I listed above. Keep in mind that the tables have metadata about the standards documents, not the standards themselves, since many standards include several documents. However, since the standards landing page is supposed to list all of the parts of the standard, and since many of these old standards are not controlled by TDWG, it might be best to just put the abstracts for the documents on the landing page along with a link to the place where you can access the standard (outside of TDWG).

Copy link
Member

@stanblum stanblum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is large complex set of updates; lots of editing for consistency, etc. Approving so that any tweaks can be made individually once all the updates are in place.

@stanblum stanblum merged commit 49f1e12 into master Jan 15, 2019
@MattBlissett MattBlissett deleted the standards branch July 27, 2020 11:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants