Add checklist of concrete things to do #1274
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Start checklist
nzdjb
reviewed
Feb 11, 2025
| > Contributed by Stuart Yeates and Max Sullivan | ||
|
|
||
| Before you start any promotion: | ||
| * Validate your OAI-PMH feed. There are a number of OAI-PMH validators which provide a third-party check of you metadata, for example: https://validator.oaipmh.com/ https://oval.base-search.net/ https://validator.dini.de/ |
There was a problem hiding this comment.
Suggested change
| * Validate your OAI-PMH feed. There are a number of OAI-PMH validators which provide a third-party check of you metadata, for example: https://validator.oaipmh.com/ https://oval.base-search.net/ https://validator.dini.de/ | |
| * Validate your OAI-PMH feed. There are a number of OAI-PMH validators which provide a third-party check of your metadata, for example: https://validator.oaipmh.com/ https://oval.base-search.net/ https://validator.dini.de/ |
| * Validate your OAI-PMH feed. There are a number of OAI-PMH validators which provide a third-party check of you metadata, for example: https://validator.oaipmh.com/ https://oval.base-search.net/ https://validator.dini.de/ | ||
| * Check your SSL certificate using one of a number of checkers, for example: https://www.ssllabs.com/ssltest/analyze.html https://www.sslchecker.com/sslchecker | ||
| * Check the ISSN details on https://portal.issn.org/ These details are very important if journal ownership becomes contested. | ||
| * Check the DOI metadata by searching for articles on https://search.crossref.org/search/ Only applies it using DOIs and getting them via CrossRef Search for an article by title and then "Actions" -> "Metadata as JSON" and check all he details. Articles can take 48 hours to appear here after registering the DOI and providing the metadata. |
There was a problem hiding this comment.
Suggested change
| * Check the DOI metadata by searching for articles on https://search.crossref.org/search/ Only applies it using DOIs and getting them via CrossRef Search for an article by title and then "Actions" -> "Metadata as JSON" and check all he details. Articles can take 48 hours to appear here after registering the DOI and providing the metadata. | |
| * Check the DOI metadata by searching for articles on https://search.crossref.org/search/ Only applies if using DOIs and getting them via CrossRef Search for an article by title and then "Actions" -> "Metadata as JSON" and check all the details. Articles can take 48 hours to appear here after registering the DOI and providing the metadata. |
There was a problem hiding this comment.
Only applies if using DOIs and getting them via CrossRef Search for an article by title and then "Actions" -> "Metadata as JSON" and check all the details.
This is a little unclear. Is this supposed to be two sentences?
| * Check your SSL certificate using one of a number of checkers, for example: https://www.ssllabs.com/ssltest/analyze.html https://www.sslchecker.com/sslchecker | ||
| * Check the ISSN details on https://portal.issn.org/ These details are very important if journal ownership becomes contested. | ||
| * Check the DOI metadata by searching for articles on https://search.crossref.org/search/ Only applies it using DOIs and getting them via CrossRef Search for an article by title and then "Actions" -> "Metadata as JSON" and check all he details. Articles can take 48 hours to appear here after registering the DOI and providing the metadata. | ||
| * Save the journal homepage to https://web.archive.org/save or similar web harvester. This will fail if you have a insitutional firewall or similar bocking external access. Important if journal ownership becomes contested. |
There was a problem hiding this comment.
Suggested change
| * Save the journal homepage to https://web.archive.org/save or similar web harvester. This will fail if you have a insitutional firewall or similar bocking external access. Important if journal ownership becomes contested. | |
| * Save the journal homepage to https://web.archive.org/save or similar web harvester. This will fail if you have an institutional firewall or similar blocking external access. Important if journal ownership becomes contested. |
| * Save the journal homepage to https://web.archive.org/save or similar web harvester. This will fail if you have a insitutional firewall or similar bocking external access. Important if journal ownership becomes contested. | ||
| * Browse the journal website with the browser console open, looking for errors or warnings that may be relavent. | ||
|
|
||
| Places to check / add your journal, if appropiate: |
There was a problem hiding this comment.
Suggested change
| Places to check / add your journal, if appropiate: | |
| Places to check/add your journal, if appropriate: |
| * Directory of Open Access Journals https://doaj.org/ | ||
| * Retraction Watch Database https://retractiondatabase.org/ | ||
| * Unpaywall https://unpaywall.org/ | ||
| * Google scholar https://scholar.google.com/ |
There was a problem hiding this comment.
Suggested change
| * Google scholar https://scholar.google.com/ | |
| * Google Scholar https://scholar.google.com/ |
jonasraoni
approved these changes
Feb 12, 2025
kaitlinnewson
requested changes
Feb 12, 2025
There was a problem hiding this comment.
Hi @stuartayeates, thanks for the pull request! I've made a review comment here about link formatting, and there are some other suggested changes here to address.
|
|
||
| Before you start any promotion: | ||
| * Validate your OAI-PMH feed. There are a number of OAI-PMH validators which provide a third-party check of you metadata, for example: https://validator.oaipmh.com/ https://oval.base-search.net/ https://validator.dini.de/ | ||
| * Check your SSL certificate using one of a number of checkers, for example: https://www.ssllabs.com/ssltest/analyze.html https://www.sslchecker.com/sslchecker |
There was a problem hiding this comment.
For any hyperlinks in documentation, please create descriptive links rather than adding raw links. You can read more in our style guide. In Markdown, the following formatting should be used:
[SSL Labs](https://www.ssllabs.com/ssltest/analyze.html)
There are multiple throughout the PR that should be converted to descriptive links.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.