get codemeta.tsv to load (displayOrder, mostly) #7844 #553
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
… watermark helptext #7844
3 tasks
poikilotherm
force-pushed
the
7844-codemeta-schema
branch
from
fcc36d0 to
1e8567d
Compare
| releaseNotes Release Notes Link to release notes https://... url <a href="#VALUE" target="_blank" rel="noopener">#VALUE</a> FALSE FALSE FALSE FALSE FALSE FALSE codeMeta20 https://schema.org/releaseNotes | ||
| contIntegration Continous integration Link to continuous integration service https://... url <a href="#VALUE" target="_blank" rel="noopener">#VALUE</a> FALSE FALSE TRUE FALSE FALSE FALSE codeMeta20 | ||
| issueTracker Issue Tracker Link to software bug reporting or issue tracking system https://... url <a href="#VALUE" target="_blank" rel="noopener">#VALUE</a> FALSE FALSE FALSE TRUE FALSE FALSE codeMeta20 | ||
| operatingSystem Operating Systems Operating systems supported (e.g. Windows 10, OSX 11.3, Android 11). text 4 FALSE FALSE TRUE FALSE TRUE FALSE codeMeta20 https://schema.org/operatingSystem |
There was a problem hiding this comment.
question: As far as I understood the spec, the compound parent field should be type "none". Would "text" cause a problem? Would that be another valid type? Is that type important after all?
(This is an interesting question despite I switched this field back to a normal, non-compound text field)
There was a problem hiding this comment.
@poikilotherm whoops! You're right. Seems like it should be "none". Sorry, I was in a hurry and just trying to get the thing to load. These TSVs are a pain in the neck! 😄
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.
fieldType and displayOrder was missing here and there, resulting in errors like this (for fieldType):
{"status":"ERROR","message":"Error parsing metadata block in DATASETFIELD part, line #8: No enum constant edu.harvard.iq.dataverse.DatasetFieldType.FieldType."}
There was a different error for displayOrder. (I didn't realize it's required.) Please double-check that the order is how you like it.
I looked at this because I'm trying to stay conscious of this branch/PR as I review this one: