access control too dependent on eml
Metacat's access control seems too dependent on EML. If I have a single
(arbitrarily or non-typed) document and I want to make it publicy readable, I
have to create an eml package with triples pointing to an access file then
insert the whole package into metacat, when all I really want to do is insert
that single file and say 'make this publicly readable'.
One way to do this is to make a generic interface that is internal to metacat
but can be subclasses by some plugin to parse specific ACL documents (like
eml-access). This generic interface would be part of the metacat API so that it
is accessible via http.
Another way to do it is to have metacat actually create access documents from
some API function, but this might run into conflict problems if a package
already has an access file.
We are going to have to retool this a bit when we start using eml2 anyway so it
would be a good time to make this interface more general.
#2 Updated by Jing Tao over 17 years ago
A new interface AccessControlInterface was created. It has generic
constants(probably some methods) for access control. Two class implements the
interface. One is AccessControlList which handle access document in data
package. The other is a new class named AccessControlForSingleFile.
A new action in metacat was created name "setaccess". The format for this
It will assign access rules in xml_access table for these docids if these
docids are not in a package.
The method we judge if a docid is in a package:
Get doctype(public id) for this docid in xml_documents. Create a variable
named packagedoctypeset in metacat.property file. In this variable it has all
public id such as:
-//ecoinformatics.org//eml-attribute-2.0.0beta6//EN and so on.
If the doctype of this id is in this set, the setaccess action will be
forbidden. Otherwise, it allows.