-
Notifications
You must be signed in to change notification settings - Fork 15
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
Centralized user and label tree repository #169
Comments
After a discussion with the Geomar people, we concluded that the centralized approach described above could indeed be a viable solution. But the most important issue in this case would be user trust. Users would have to be able to trust the entity which maintains BIIGLE with their data (if not their images). This is a similar situation like Pangaea which is maintained by a central authority.
|
Continued in #208. |
Goal: Users should be able to use their user account, label trees and projects in every BIIGLE instance.
This goal is in conflict with our current approach of decentralized BIIGLE instances and transfer of data via import/export. One possible idea for implementation is this:
This is based on the assumption that the only motivation of the institutions currently maintaining their own BIIGLE instance is that they don't want to publish their images.
I don't really like this idea as the current decentralized solution has some benefits, too. I doubt that Senckenberg and Geomar want to give up their instances. If they don't, we don't gain anything but additional complexity by the implementation of the idea described above.
The text was updated successfully, but these errors were encountered: