Bug #22

content negotiation for doctypes needed

Added by Matt Jones over 20 years ago. Updated over 18 years ago.

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


Estimated time:


Need to mechanism to express the types of documents that should be returned from
a metadata query. For example, a client should be able to specify that they
only want to see documents of type eml-dataset returned as the result of a
query. The doctype should be specified as a Public Identifier. This should be
incorporated into the pathquery.dtd as an indication of the type of content that
the user wants returned. This feature will require backtracking from the
documents found to related documents using the relations element, which is being
re-worked as a distinct module for packaging metadata.


#1 Updated by Matt Jones over 20 years ago

Will work this into DBSimpleQuery and into the query language -- mbj

#2 Updated by Matt Jones over 20 years ago

added content negotiation to DBSimpleQuery. Web forms updated to demonstrate
feature by selecting only eml-dataset datasets. Feature works. backtracing
fromone document type to another is not implemented yet because it depends on
the final form that metadata packaging takes. need to add it to the
pathquery.dtd query syntax so that more complex queries can indicate a return
type that is acceptable. -- mbj

#3 Updated by Matt Jones over 20 years ago

Both DBSimpleQuery and, more relevant, DBQuery support specification of the
document type that should be returned as a result set. The DBQuery mechanism
involves listing the document types that are to be returned in "returndoctype"
elelemnts in the XML query representation. Backtracing hits to other document
types still not supported because it requires the package linking features.
Will enter a new bug for that feature request.

#4 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 22

Also available in: Atom PDF