Make website generic/reusable

[niconoe]

I am wondering if it wouldn't be a good contribution to the broader community to actually make the RIPARIAS Early Warning tool as generic as possible (different species / country of interest).

Concretely, that would mean splitting the repository in two:

• a generic, reusable tool (with documentation for non-riparias interested users)
• a "configuration" repository for RIPARIAS early alert that can be applied to the tool above with just the specific points (country of interest, list of species, credentials at GBIF, static texts, colors, ...)

Any opinions?

[damianooldoni]

This seems a very interesting idea.

[niconoe]

@timadriaens / @peterdesmet / @LienReyserhove (others welcome too!):

Since you know the potential users much better than me: do you think this idea (promoting an improved version of the RIPARIAS alert tool that can be relatively easily configured and deployed for other regions/species of interest) would generate solid interest in the "invasive community" or not?

Also curious about some details (why/why not, factors that would make that easier, ...)

Thanks!

[timadriaens]

It seems a bit stupid to make such a tool only for the RIPARIAS project area indeed although I can see some advantages as well of keeping the project scope. But if you think about it, would it not make more sense to include such alert possibility as a tool in GBIF altogether? Seems something for an Ebbe Nielsen challenge...

[timadriaens]

solid interest in a generic tool: potentially yes. Many people however kind of "distrust" gbif as a data source and put it away as a "poubelle" of many types of data with heterogeneous quality (we have to acknowledge that we are spoiled in that respect in Belgium).

the alert tool now only allows you to select datasets (which is good). If you make a generic one, you probably can use all the filtering options already available within GBIF (e.g. basis of record etc.).

one other thought: such a generic gbif tool might function more as a "publication of data-early warning".

[peterdesmet]

Tim answered this better than I could. Could be a useful Ebbe Nielsen though.

[niconoe]

FYI, I've started ground work for this (I plan to achieve this incrementally, while working in parallel on other features). For now the main concrete tasks are:

• rename stuff in code: variable, functions, files, ... now use the pterois name rather than riparias. When done, the RIPARIAS string should appear only into configuration, not the engine code
• move hardcoded things (site name, colors, map configuration, ...) into the configuration

[damianooldoni]

Thanks @niconoe to inform me about progress on this work. Yes, I agree to do this in parallel to other tasks as indeed discussed earlier.

You can continue to update me about this work in this issue. Maybe you can create a checklist if you already know more or less the steps?

[niconoe]

Long done!