You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The NASSA schema should be formalized and versioned. The .yml file should get a field nassaVersion
If the keywords in subjects, regions, periods, modellingKeywords and programmingKeywords should be standardized and enforced, then we need a mechanism for that
create a template yml file with all possible fields so module authors can copy it and adapt it more easily. The template should note which nassa-hs version it refers to.
Details:
"Netlogo" should be renamed to "NetLogo"
More programming languages beyond R, Python and NetLogo should be allowed
When the format of the id field is clear, it should also be validated
Some fields have length limits, which should be checked (title: 100c)
The reading function should check if the files/dirs listed in readmeFile, docsDir and designDetailsFile actually exist
Software:
add some unit tests for the parsing code
The text was updated successfully, but these errors were encountered:
Bigger issues:
nassaVersion
subjects
,regions
,periods
,modellingKeywords
andprogrammingKeywords
should be standardized and enforced, then we need a mechanism for thatDetails:
id
field is clear, it should also be validatedreadmeFile
,docsDir
anddesignDetailsFile
actually existSoftware:
The text was updated successfully, but these errors were encountered: