-
Notifications
You must be signed in to change notification settings - Fork 5
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
Adding maintained
field to schema
#420
Comments
In #421, I was able to set |
I have bumped the schema and set the |
closed with #423 |
Ok. We can leave the issue "closed," while continuing to update our records. Should just remember to follow up with Jonas about publishing another release of our schema and database. |
Reopened for release task |
Reopened because I still need to do the release :P |
Sure! My bad |
Made a release: https://zenodo.org/records/10391227 |
I did the first steps of this in #419. There is now a
maintained
field, pretty much at the top level of the schema. I didn't see an existing category in which it seemed to belong.maintained
is currently defined as a nullable boolean. i.e., it should betrue
orfalse
, but it can optionally benull
, at least for the time being, while we work to update existing entries.I've also added this field to every current database entry. And it's
null
everywhere—but this is just a starting point. All tests are passing, and we can improve our data over time. I do have some ideas for detecting entries for whichmaintained
must betrue
. For example, we can search for projects that have defined funding periods that are still active. I would be comfortable saying that currently funded == maintained. (The entire problem is that the inverse does not hold…)Anyway, if this field doesn't work out for one reason or another, or if it proves more hassle than it's worth, we can always remove it. @XeniaMonika, we should probably bump the schema version (to
0.2.2
?). @Jomula, this may become an occasion for publishing new releases on GitHub and Zenodo.The text was updated successfully, but these errors were encountered: