Details
-
Story
-
Resolution: Fixed
-
Major
-
None
-
None
Description
We should simplify the rather ambitious current ActionType defined in the message-xml Bitrepositoryelements to a simple enumeration. The is the same strategy we used in the Alarm definitions, where the idea was to not model overly complicated event structures in the pillars, but rather delegate the responsibility of categorizing event to any client subscribing the the event information.
While solving this issue we should also trim to scope to only focus on file access events on the pillars. This is contrary to the earlier 'stuff which perhaps should be logged' audit trails/log scope.
Attachments
Issue Links
- Trackbacks
-
![[Confluence: Bitrepository]](/jira/images/icons/generic_link_16.png "[Confluence: Bitrepository]")
2011-12-21 Videomeeting
Tidspunkt: Onsdag 20111221 10:30 12:00 # Agenda ok? # Er der en grænse for hvor store filer vi kan overfører vha. http? (SA Jonas). # Skifte til at bruge simple enum type for AuditTrail ActionType,...
-
2012-01-04 Videomeeting
Tidspunkt: Onsdag 20120404 10:30 12:00 # Agenda ok? # Er der en grænse for hvor store filer vi kan overfører vha. http? (SA Jonas). # Skal protokollen have mulighed for at vi kan få oplyst filesize på de enkelte filer? Kim opdatere. Ok, som optional....
