Feature #7099

Create a new admin page for Metacat admins to register schemas

Added by Jing Tao over 2 years ago. Updated over 2 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Currently we add new schemas base on Metacat release sand occasionally add it by sql commands.
We will disable Metacat to download external schemas and reject a xml object if the schema of the object can't be found locally.( So we believe the request of adding new schemas will increase. We need provide a admin page to register schemas.


#1 Updated by Jing Tao over 2 years ago

The schema locations is /tomcat-home/webapps/metacat/schema (in order to be accessible by the http), so the new installation of Metacat may delete the schemas added by this page. It will create the scenario - the xml_catalog has the record but the schema file itself has been gone.

The solution I am thinking is the registry process will create two copies of the schema, one is in /tocmat-home/webpass/metacat/schema; the other is in /var/metacat/schema. If the copy of /tocmat-home/webpass/metacat/schema is gone, Metacat can copy it back from /var/metacat/schema.

#2 Updated by Matt Jones over 2 years ago

I think this is a good idea, but I think we should go the other way -- have the copy in wepapps/metacat/schema be the 'shipped' version, and copy those on Metacat start to /var/metacat/schemas, and use that as the official 'local' copy.

#3 Updated by Jing Tao over 2 years ago

This is good idea - we can avoid to create two copies of registered schemas in the registry process and the scenario that registered schemas are deleted. However, the /var/metacat/schemas is not accessible by Apache by default, so we have to set the schema location by the file protocol. Also it is hard for users to look at the schema itself.

#4 Updated by Jing Tao over 2 years ago

  • Target version changed from 2.8.0 to 2.9.0

Also available in: Atom PDF