Re: [Dspace-tech] Are you using the DSpace History System?
Hi Mark, This is a survey to see if anyone is actually utilizing the existing History System in production. If you are using the history system, would you please be kind and respond with a quick sentence on how your applying it? I am not currently using it, but bringing it up is timely because I'm reaching a point where what I am being drawn towards is the necessity of an audit tool for certain system activities. I haven't had time to evaluate what the history system can do for me in that regard, but if anyone is planning on making changes to it, I'd be interested in being involved in some way, shape, or form. Let me give you one or two examples of the kind of auditing that I need: as users add/remove files over time from their item as they prepare it, I need to track what was added/removed and by whom when (multiple users can work on a single item in our system). Similarly for licences. Also, administrators perform many tasks on items before they hit the public repository, and a navigable audit trail on item activities which can actually be interacted with would be of great benefit. Cheers, -- Richard Richard Jones| t: +44 (0)20 759 [48614 / 41815] Web Database | e: [EMAIL PROTECTED] Technology Specialist | b: http://chronicles-of-richard.blogspot.com/ Imperial College London | - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Are you using the DSpace History System?
Dear Richard et al., On Wed, 2007-03-07 at 23:27, Richard Jones wrote: Hi Mark, This is a survey to see if anyone is actually utilizing the existing History System in production. If you are using the history system, would you please be kind and respond with a quick sentence on how your applying it? I am not currently using it, but bringing it up is timely because I'm reaching a point where what I am being drawn towards is the necessity of an audit tool for certain system activities. I haven't had time to evaluate what the history system can do for me in that regard, but if anyone is planning on making changes to it, I'd be interested in being involved in some way, shape, or form. Let me give you one or two examples of the kind of auditing that I need: as users add/remove files over time from their item as they prepare it, I need to track what was added/removed and by whom when (multiple users can work on a single item in our system). Similarly for licences. Also, administrators perform many tasks on items before they hit the public repository, and a navigable audit trail on item activities which can actually be interacted with would be of great benefit. A decent version control system for DSpace is a must. Not only should one be able to track the changes over time to each document, but one has to be able to consult and revert to previous versions. This functionality is taken for granted with any decent Enterprise Content Management (ECM) platform. In the hope that they might provide some pointers, I have uploaded a couple of screenshots of a document's `Status History' available within the IeB ECM system (powered by CPS-3.4/Zope): (http://indica-et-buddhica.org/sections/repositorium/desired-features/versioning-system) The current incarnation of CPS -- Nuxeo 5 -- is an open source Java app.. It is possible that some of the version control code could be modified by the DSpace community: (http://www.nuxeo.org/sections/about/) Best regards, Richard MAHONEY -- Richard MAHONEY | internet: http://indica-et-buddhica.org/ Littledene | telephone/telefax (man.): +64 3 312 1699 Bay Road| cellular: +64 27 482 9986 OXFORD, NZ | email: [EMAIL PROTECTED] ~~~ Indica et Buddhica: Materials for Indology and Buddhology Repositorium: http://indica-et-buddhica.org/repositorium/ Philologica: http://indica-et-buddhica.org/philologica/ Subscriptions: http://subscriptions.indica-et-buddhica.org/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Are you using the DSpace History System?
Have a look at the wiki page about the new history system: http://wiki.dspace.org/index.php/HistorySystemPrototype It's already written, and in fact the project is over so I won't be doing any more work on it. If the Event patch gets adopted, it will remove the old history system, but open the way to let sites install this one as an add-on. Right now it only exists in the wiki and on the patch queue. The old history system wrote some very dodgy records; some outright errors, other records that cannot be correlated to actual events, and it used database IDs as identifiers instead of anything persistent. (iirc, one of its worst sins was using Handle-like identifiers with database-IDs in the suffix). So, if you're actually going to use the data you're better off with the new system. It also includes an RDF database (Sesame2) so you can make custom queries, which sounds like it would help your use case. -- Larry I am not currently using it, but bringing it up is timely because I'm reaching a point where what I am being drawn towards is the necessity of an audit tool for certain system activities. I haven't had time to evaluate what the history system can do for me in that regard, but if anyone is planning on making changes to it, I'd be interested in being involved in some way, shape, or form. Let me give you one or two examples of the kind of auditing that I need: as users add/remove files over time from their item as they prepare it, I need to track what was added/removed and by whom when (multiple users can work on a single item in our system). Similarly for licences. Also, administrators perform many tasks on items before they hit the public repository, and a navigable audit trail on item activities which can actually be interacted with would be of great benefit. Cheers, -- Richard Richard Jones| t: +44 (0)20 759 [48614 / 41815] Web Database | e: [EMAIL PROTECTED] Technology Specialist | b: http://chronicles-of-richard.blogspot.com/ Imperial College London | - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
