I think "projects" will end up being somewhat complex in a real life scenarios.
Users will want to divide up various sources of annotations.
The basic structure would be:
Project
ruleset
ruleset
ruleset
...
For example,
Project : legumedata.org working group annotations
ruleset : "Joe Miller's annotations from personal observations"
ruleset : "Hand made annotations from the legume working group"
ruleset : "Modified iucn range maps"
ruleset : "WCVP"
ruleset : "Country centroids are suspicious"
ruleset : "Ocean is suspicious"
ruleset: "Botanical gardens are suspicious"
ruleset : "GBIF annotations from portal feedback"
Having the ability to choose which rulesets you import into your project would also allow users to construct complex cleaning scripts that borrow from other rules (like the ocean polygon example).
This complexity still comes at a cost to users who might not need or want to deal with it. So I still think having a general catch-all bucket for user supplied annotations would be useful (Project : "default": ruleset : "default").
I think "projects" will end up being somewhat complex in a real life scenarios.
Users will want to divide up various sources of annotations.
The basic structure would be:
Project
For example,
Project : legumedata.org working group annotations
Having the ability to choose which rulesets you import into your project would also allow users to construct complex cleaning scripts that borrow from other rules (like the ocean polygon example).
This complexity still comes at a cost to users who might not need or want to deal with it. So I still think having a general catch-all bucket for user supplied annotations would be useful (Project : "default": ruleset : "default").