Metacat

To avoid id generation conflicts happening at the same millisecond, append a 5 character random string to the end of the docid.

retry: add node name in the correct order for predicate navigation
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5561

add node name in the correct order for predicate navigation
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5561

handle queries with predicates correctly.
when docids are used in the return field look up, we need to make sure they are included in the values in the correct order for their corresponding parameter place holders (?)

close prepared statement only if not null
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5562

Use accessblock in setaccess method. So user can grant/revoke public readable access.

ensure that the revision list is ordered ascending in case someone changes the sql query without realizing that it matters...

set the byte size of the ORE map before adding it

set/update the obsoletes/obsoletedBy fields in system metadata so that we always have a complete revision history for each object.
Note: ORE maps do not have revision history...yet(?)

order the revision list, ascending.