search

paleobot / pbot-dev

Codebase and initial design documents for pbot client
MIT License
2 stars 2 forks source link

Project Node: updated from "Distinguish between public and group" #94

Open aazaff opened 1 year ago

aazaff commented 1 year ago

Currently once an item is made public we remove it from all other groups. This does not actually make sense since an object needs to be associable with multiple nodes; if public is selected then the info is public! public/private is slightly different than being in groups.

This may require some significant rework of certain backend systems related to delete and versioning.

doricon commented 1 year ago

Just a further note that currently the groups field drop down list has 'public' in the list. We mentioned in the meeting this past week that it doesn't make sense that there was a check box for public but it was also in the drop down. This was identified as a bug, but I realized why it may be in the drop down - when you are doing a search, you want to be able to search in both public group and private group data (I had to do that yesterday). Currently that is only possible if 'public' is also in the field drop down list.

doricon commented 1 year ago

This has evolved into the idea of implementing a "Project" node. collections/specimens/OTUs can belong to one or more Projects.

Projects would have: Project Name Short description of project Reference (optional?) People? (not for access, just for recording the workers of a project)

Projects is separate from access Groups.

doricon commented 1 year ago

As a note, this Project node would be very helpful for Pbot functioning as a repository - publications could reference that their data is available in Pbot under the Project XXX