Closed jonquet closed 8 months ago
Those groups are not empty and contain consecutively 23 and 6 ontologies.
Another problem is that there is no easy way (a script) to remove (or add and manage) groups
Yes. But the groups are not used (AGROLD) and do not represent a relevant grouping anymore (RICE). We can delete the groups... and its the occasion to check if the metadata of each ontologies within these groups is automatically updated. Maybe we can save somewhere the list of the 6 and 23 ontologies, just in case we need to do this manually afterwards.
in the API we have the following endpoints
get "/groups"
get '/groups/:acronym'
patch '/groups/:acronym'
delete '/groups/:acronym'
Is it a good idea in the UI to add an admin panel to manage groups? @jonquet
Otherwise, I will just remove them using the API
Is it a good idea in the UI to add an admin panel to manage groups? @jonquet
Yes I think it will be necessary. We would need a simple a UI to manage Groups, Categories and Slice. Eventually this view will become a way to "setup" the portal and write the config files.
You have now @jonquet , those UIs to manage the groups and remove agrold and rice, if not already done.
Group RICE and AGRO-LD removed.
@SirineMhedhbi Seems the Groups have been well erased https://data.agroportal.lirmm.fr/groups/RICE But, the ontologies still have the zombie assigned: https://data.agroportal.lirmm.fr/ontologies/CO_320?display=group
This is a bug I believed.
@syphax-bouazzouni Can you clean up the code (old homepage listing maybe) and listing (HTTP redirects) for the corresponding 2 slices?
Hi, wrong syphax?
Slices https://data.agroportal.lirmm.fr/slices, cleaned. For HTTP redirects it is on the level of STI-RX.
We can delete the RICE and AGROLD groups. They are not really used and we use the notion of groups slightly differently now.