-
Notifications
You must be signed in to change notification settings - Fork 3
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
DOI url bug between ckan and metadata form #230
Comments
hope my issue is clear, otherwise, don't hesitate to contact me |
It appears that I need to adjust the parsing of DOI's in CKAN. I thought this was working but perhaps I'm not accounting for the dashes. On a related note, it would be very convenient if the metadata form stored the full URL in the XML rather than just the identifier. Could we change the DOI input in the metadata form to allow/encourage full URLS? |
"Could we change the DOI input in the metadata form to allow/encourage full URLS?"I agree with Mat as it would also be helpful when we use the eml for OBIS IPT, right now, I have to correct it manually |
I agree as well, it should come out as a complete URL in the XML/YAML/EML/ERDDAP outputs |
Reopening this - one last step needed is any records that have been saved without the https://doi.org/ prefix need to be update in the database to include it. Otherwise these records appear as "invalid" in the metadata form, and eg can't use the download to XML/EML options |
I think the database update has been done, need to confirm. |
It looks like all DOI URLs have been updated - though I did identify that there are ~120 entries that have that field populated with a non-DOI entry e.g.
vs
Is this something that needs to be addressed as well? |
I think that is ok for us but is perhaps something that @Br-Johnson, @timvdstap and @JessyBarrette should know about for eh future |
Thanks @fostermh @BryceMarshall Yes will address that in a coming sprint :) At least of the Hakai specific related one for now |
When we put the DOI url in the form: https://doi.org/10.26071/ogsl-m3x6-fh43
it says that the entry is not correct
However, if we only put the number:10.26071/ogsl-m3x6-fh43, then there is a problem in the catalog
without url
with url
The text was updated successfully, but these errors were encountered: