added ISSN-L as an alternative value for lissn #11638
Closed
+1
−1
Conversation
This file contains hidden or 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
ofahimIQSS
moved this from Ready for Triage
to Ready for Review ⏩
in IQSS Dataverse Project
Member
Author
|
Following the Zulip discussion, another approach will be used : changing the values displayed in the UI rather than adding an alternative value. |
Member
|
@DS-INRAE great, looking forward to the new PR! Closing. |
github-project-automation
bot
moved this from 🚧 Dev by Recherche Data Gouv
to Done
in Recherche Data Gouv
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What this PR does / why we need it:
Following incertainties on the identifier behind "lissn" (cf. Zulip topic ), adding an alternative value "ISSN-L" to lissn for future reference.
Special notes for your reviewer:
Similar to other alternative values additions to the tsv file, e.g. #8689
Is there a release notes update needed for this change?:
No