1. More functional AUDIT datastream
    1. API Endpoint to access the stream
      1. Currently no good way to access the Audit information.
    2. PREMIS support
      1. More information in the Audit DS would provide better direct support.
      2. For example, Islandora MS actions are recorded in a separate file, but there is no easy way to get that information into the Audit DS.
    3. This could also help Fedora to build a TRAC complaint repository.
      1. public.ccsds.org/publications/archive/652x0m1.pdf

2 Comments

  1. Neil Jefferies

    The AUDIT datastream needs to support arbitrary events which can be inserted by external agents performing things like preservation actions. PREMIS is a moving target anyway so a more open pluggable method of generating audit events (besides the CUD operations that are intrinsic to FEDORA) would be sensible.

    We have the need to record other time-based information such as access statistics as retention policies can be based on last-accessed time.

     

  2. Matthias Razum

    > We have the need to record other time-based information such as access statistics as retention policies can be based on last-accessed time.

    Do we want this information to be part of the object itself, or is this rather related information we want to store separated from the object? I agree that this kind of information is crucial, though.

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.