Since we are only dealing with a fixed set of thesauri, the form should require as input:
a thesaurus name, selectable from a dropdown list, containing all the thesauri names needed in this extension (see the README)
a file upload entry where the RDF file will be selected.
The loading page should run the same logic executed by the upload theusarus command line.
We can run the loading synchronously.
As an output, we want a report of
how many items have been added (if the key was not present)
how many localized entries have been updated (for existing keys)
how many items have been removed (entries no longer available in the loaded RDF but existing in the DB)
how many items should have been removed but haven't (entries no longer available in the loaded RDF but existing in the DB, but referenced in some dataset)
We can do that by adding a "thesaurus" tab to the admin page.
Here an example about how to add a tab (the referenced "azure_admin" is defined in this Blueprint declaration).
Since we are only dealing with a fixed set of thesauri, the form should require as input:
The loading page should run the same logic executed by the upload theusarus command line. We can run the loading synchronously. As an output, we want a report of