Project

General

Profile

Feature #7669

The use of formatId to indicate the schema variant that should be used for validation of metadata.

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

Status:
Closed
Priority:
Normal
Assignee:
Category:
Metacat
Target version:
Start date:
2016-03-03
Due date:
% Done:

100%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

Currently Metacat uses the namespace as a key to identity the schema files for validation of metadata. However, in practice some schemas have the same namespace but the schema themselves are different. So we need to design and implement a solution that supports the use of formatId to indicate the schema variant that should be used for validation of metadata.

History

#1 Updated by Jing Tao over 8 years ago

  • Category set to Metacat
  • Status changed from New to Closed
  • % Done changed from 0 to 100

In xml_catalog table, we added a new column called formatid. If a format id represents a variant, the format id value will be stored there and a different schema location is stored in the column system_id. So the same namespace with different format id (it can be null if it is not a variant) can have different schema files for validation.

When an object is created, the format id in the system metadata will be checked. If it matches on on the xml_catalog table, that set of schemas will be used. Otherwise, we will use the old way to do validation.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)