[ 
http://jira.dspace.org/jira/browse/DS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10312#action_10312
 ] 

Mark Diggory commented on DS-203:
---------------------------------

Login/out of EPerson should be a UsageEvent.

The R in CRUD should be a Usage Event 

We should consider how Usage Events relate to change events and how we can 
improve the whole api/implementation to support extensible events.  I dislike 
the hardcoding of available event types and the object they can occur on in the 
Constants and Event Manager.  We should consider moving away from byte offsets 
as a means to identify events and instead focus on Enum's or using OO to 
express the events being transported.

The Current Event system will not be portable to 2.0, and in 2.0 Aaron has 
implemented a different solution to Event management that is much more generic. 
 I would consider that an appropriate venue over 1.6 to attain the refactoring 
I'm recommending.  My point is just that the next generation of DSpace won't 
use this EventManager so investing time into adjusting it should take into 
consideration that it will end-of-life in 1.x.

Mark




> Extend the event system to no CRUD actions
> ------------------------------------------
>
>                 Key: DS-203
>                 URL: http://jira.dspace.org/jira/browse/DS-203
>             Project: DSpace 1.x
>          Issue Type: Improvement
>          Components: DSpace API
>            Reporter: Andrea Bollini
>
> I think that we need to extend the event system to cover also no "CRUD" 
> actions on content object.
> I'm thinking to events related to "status transactions" of an item (or more 
> appropriately of an InProgresSubmission) like these:
> - installation
> - start of workflow process
> - reach of step 1, 2, 3
> Also other events could be fired like login / logout of an eperson...
> Please add here your comments and vote for this issue if you like to see more 
> efforts in this direction

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to