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

Authors in List of Terms header must agree with data source in rs.tdwg.org repo #88

Open
baskaufs opened this issue Jun 18, 2024 · 1 comment
Assignees
Labels
StaDocGen Technical Issues strictly technical in nature, unrelated to the content of the standard itself.

Comments

@baskaufs
Copy link

In an effort to ensure that the metadata in standards document headers agree with the machine-readable metadata about the documents, we have moved to inserting the metadata into the headers from source files in the rs.tdwg.org repository. In the case of authors, the data are found in the authors_configuration.yaml file in the appropriate directory for the file.

In the case of the Latimer Core List of Terms document, that file is located here, which was updated in tdwg/rs.tdwg.org#162 based on the file submitted by the Task Group. The current draft of the List of Terms lists some different authors and also does not include the hyperlinks to the author ORCIDs and the institutional affiliations provided in the YAML file.

For an example, see the Darwin Core List of Terms, which draws from this YAML file.

Note that the pattern for the directory name mimics the permanent URL of the doc, but with underscores replacing slashes, e.g. http://rs.tdwg.org/dwc/doc/list/ is in the directory dwc_doc_list. In the case of the current LtC List of Terms doc, since it's been ratified, the YAML file is available in the master branch. However, to provide flexibility in generating list of terms docs that aren't yet ratified, it should be possible to specific that the build script look in a different branch (perhaps as a command line argument).

@rondlg rondlg added the Technical Issues strictly technical in nature, unrelated to the content of the standard itself. label Jul 11, 2024
@ben-norton ben-norton self-assigned this Jul 11, 2024
@magpiedin
Copy link
Contributor

@baskaufs -- Did you need us to follow up on this, or does someone need to handle it on the rs.tdwg.org side?

(Sorry if I missed a step!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
StaDocGen Technical Issues strictly technical in nature, unrelated to the content of the standard itself.
Projects
None yet
Development

No branches or pull requests

4 participants