Developers,

I'm looking at the 2.0 Event model in comparison to the 1.x Event
model and I am seeing some discrepancies that I think need addressing:

DSpace 1.x events provide a triple of event object, event action and
event subject so that, for instance, the following can be recorded
easily:

dspace:collection/1234.5/1 Action.REMOVE dspace:item/1234.5/2

See: 
https://scm.dspace.org/svn/repo/dspace/trunk/dspace-api/src/main/java/org/dspace/event/Event.java

And this is stored within the Event because later in the event
processing the detail that the item was part of the collection has
already been lost.  Its also almost always the case that the events in
dspace have this nature of activities that are recordable as triples.

site add community
community add collection
collection add item
item add resourcepolicy
group add user
user update name
item update field
collection update field
user login site
user view item

I think it is very important we retain this in 2.0 but I do not see
this in the 2.0 event api at the moment.

See: 
https://scm.dspace.org/svn/repo/dspace2/core/trunk/api/src/main/java/org/dspace/services/model/Event.java

I propose we make sure to get the DSpace 2.0 Event to explicitly
capture the same state in the same model so that we can retain the
explicit detail we need throughout DSpace 2.0 to properly record
events in their context.  I do notice that properties can be attached
to the event, but I consider this an very important aspect of an event
that is always required and should be expressed within the API.

thoughts?
Mark

-- 
Mark R. Diggory
@mire - http://www.atmire.com

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to