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

What to do with labs and tools? #730

Open
MortenHofft opened this issue Dec 12, 2024 · 0 comments
Open

What to do with labs and tools? #730

MortenHofft opened this issue Dec 12, 2024 · 0 comments
Labels
GBIF.org parity Required to replace GBIF.org question Further information is requested

Comments

@MortenHofft
Copy link
Member

MortenHofft commented Dec 12, 2024

We need to decide what to do with this and tools more broadly.

we could

  • keep the angular tool running for a while
  • implement it on the new gbif.org stack
  • move labs projects to separate projects that are maintained or not outside of gbif.org code
    • pro: reimplementing gbif.org doesn't not have to reimagine all lab projects.
    • con: they won't be maintained along with the core product

Some tools is so integrated that it makes sense to keep them on gbif.org, others are more fringe experiments that could have their own live.

Remove it

  • Relative observation trends feels like it would live just fine on its own as a lab experiment. could be external tool. Or just remove it.
  • machine vision demo
  • data repository

Part of gbif.org

  • suggest a dataset makes sense to have part of gbif.org
  • occurrenec snapshots: part of gbif.org
  • derived datasets should be part of gbif.org I would think
  • species matching is somewhere in the middle, but I can see how we might want to integrate it more into search (like searching for a long list of names)
  • sequence ID: given our increasing focus on sequences, it might make sense to keep it close to the core.

Could be external

  • name parser: could be external tool.
  • data validator: could be external, could be core. I'm open to both.
    If it is something Hosted portal participants are interested in branding, then having it as part og gbif.org code would make sense. The results are tried to my profile, so as such it could make sense to integrate. But we could also just add login elsewhere.

If we decide to have external tools in the mix, then we should agree on a common way we brand them and link back to gbif.org
Ideally taking something from a shared folder like styling or even html

@MortenHofft MortenHofft added GBIF.org parity Required to replace GBIF.org question Further information is requested labels Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GBIF.org parity Required to replace GBIF.org question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant