Skip to content
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

Closed
theodore-s-beers opened this issue Dec 12, 2023 · 8 comments · Fixed by #423
Closed

Adding maintained field to schema #420

theodore-s-beers opened this issue Dec 12, 2023 · 8 comments · Fixed by #423
Assignees

Comments

@theodore-s-beers
Copy link
Collaborator

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 be true or false, but it can optionally be null, 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 which maintained must be true. 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.

@theodore-s-beers
Copy link
Collaborator Author

In #421, I was able to set maintained to true for 56 entries (or some number close to that). I just wrote a script to identify projects that have defined funding periods that continued at least into 2023. Those are now marked as maintained as a matter of course. Separately, it occurred to me that most organizations—though not all—remain active over a longer period of time. So I looked at those as well, and felt comfortable setting maintained to true in all but a few cases.

@XeniaMonika
Copy link
Collaborator

I have bumped the schema and set the maintained value to false for 11 projects I have already marked as such during my research for the taxonomy.

@XeniaMonika
Copy link
Collaborator

closed with #423

@theodore-s-beers
Copy link
Collaborator Author

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.

@Jomula
Copy link
Contributor

Jomula commented Dec 14, 2023

Reopened for release task

@Jomula Jomula reopened this Dec 14, 2023
@Jomula Jomula self-assigned this Dec 14, 2023
@Jomula
Copy link
Contributor

Jomula commented Dec 14, 2023

Reopened because I still need to do the release :P

@Jomula Jomula reopened this Dec 14, 2023
@XeniaMonika
Copy link
Collaborator

Sure! My bad

@Jomula
Copy link
Contributor

Jomula commented Dec 15, 2023

Made a release: https://zenodo.org/records/10391227

@Jomula Jomula closed this as completed Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants