Do not insert all oid prefixes on db creation level

[cymed]

General

• Fix a bug

Context

It is not a good practice to store the oid prefixes in the main datamodel. The sysadmin should add their own prefixes to their datbase instead

Describe your changes

Remove provided oid prefixes

Screenshots

Issue ticket number and link

Checklist before requesting a review

• I have performed a self-review of my code
• If it is a core feature, I have added thorough tests.
• CI Tests are green
• The documentation is up to date with the proposed change.
• My work is ready for review

Checklist before merge

• A review has been performed
• Comments are resolved
• Documentation is ready

[ponceta]

I feel we should ease as much the configuration of things at least for TEKSI users and why not preconfigure oid prefixes?
We discussed about having an oid prefix switch in the TMMT so having several sample oid prefixes is a nice thing at least for testing purposes.

[cymed]

I feel we should ease as much the configuration of things at least for TEKSI users and why not preconfigure oid prefixes? We discussed about having an oid prefix switch in the TMMT so having several sample oid prefixes is a nice thing at least for testing purposes.

It is ok to have some fake oids for testing purposes, but I do not see an advantage in centrally storing all prefixes

[ponceta]

In TMMT, I would like to be able to set the oid prefix from a dropdown / search menu :

Being a TEKSI member would enable you to have your oid_prefix already in that list without having to do sql or pgAdmin stuff.

[cymed]

In TMMT, I would like to be able to set the oid prefix from a dropdown / search menu :

Being a TEKSI member would enable you to have your oid_prefix already in that list without having to do sql or pgAdmin stuff.

I think it is better to have a GUI allowing to set that value instead. You'll have to do it once and nobody else needs that information.