You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
We need to decide what to do with this and tools more broadly.
we could
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.orgoccurrenec snapshots
: part of gbif.orgderived datasets
should be part of gbif.org I would thinkspecies 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
The text was updated successfully, but these errors were encountered: