We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Depends on #79 and may better be split up into multiple issues when started.
The venue landing page should show some minimal metadata about the venue. Currently, the page only lists the checks:
https://codecheck.org.uk/register/venues/conference/AGILEGIS/
It should also provide the following information:
The final page cold look something like this:
The information should be stored in plain text files in the register, e.g. in a folder venues with YML files, such as gigascience.yml:
venues
gigascience.yml
type: journal contact: name: Edd Editor email: [email protected] url: https://giga.science logo-url: https://giga.science/logo.png identifiers: - name: ROR value: bla link: http://ror.org/bla - name: ISSN value: 1234-5678 link: https://issn.org/1234-5678 description: | The journal is...
The text was updated successfully, but these errors were encountered:
nuest
No branches or pull requests
Depends on #79 and may better be split up into multiple issues when started.
The venue landing page should show some minimal metadata about the venue. Currently, the page only lists the checks:
https://codecheck.org.uk/register/venues/conference/AGILEGIS/
It should also provide the following information:
The final page cold look something like this:
The information should be stored in plain text files in the register, e.g. in a folder
venues
with YML files, such asgigascience.yml
:The text was updated successfully, but these errors were encountered: