Fedora Commons

committed fixes to trunk r6557 and maintenance-2.2 r6558

Fixed bug in tasks 145707 (trunk) and 145936 (maintenance-2.2),
ingestObject and modifyObject now create audit records which include the
provided log message. The log message for purgeObject is written to the
server log. In order to allow the choice to create an audit record on
object ingest or not, an audit record will only be created if a log message
is provided. If no log message is provided on the call, no audit record is
created.

Audit records are now created for all API-M methods which update the object
with the exception of addRelationship and purgeRelationship. Some
discussion will be necessary to determine if providing audit records on
these methods is appropriate.

All API-M methods in 3.0 now log a completion notice at the INFO level
which includes any provided log message (this is only done for purgeObject
in 2.2.)

Normally, API-M methods that do object modification will result in a new
audit
record in the object. This is true for all component (datastream and
disseminator) methods, but in the case of the following methods, the
logMessage
is not recorded anywhere:

- ingestObject
- modifyObject
- purgeObject

Note that for purgeObject, it makes no sense to put the audit record in
the
object. Something else needs to be done, like writing it to the system
log.