Hi Stephen / Tim / all, Most actions are logged to the DSpace log, so another approach might be to look into log analysis tools. (At least that's how it worked up to DSpace 6 but I assume it's still the case in 7.) In order for that approach to make sense, some of the logging messages may need to be improved / adjusted for the information to be meaningful - most log messages include internal DSpace IDs that may need to be resolved against the DSpace database, etc.
cheers, Andrea On Fri, 3 Mar 2023 at 06:41, 'Tim Donohue' via DSpace Community < [email protected]> wrote: > Hi Stephen, > > At this time, DSpace doesn't have a full "audit trail". DSpace does > capture *some common events* (like original creation/deposit, workflow > approval events, etc) in the "dc.description.provenance" metadata field > (which is only visible to Administrators). But, it's not a full audit > trail of every change made to an Item (e.g. later Item modifications after > the Item is deposited are not currently tracked in > "dc.description.provenanace"). It is also possible for you to manually add > your own notes into "dc.descripton.provenance", but only a limited set of > events are tracked automatically. > > Honestly, I think it would be possible for someone to enhance DSpace to > provide a more complete audit in this same "dc.description.provenance" > field (or a similar field). I also suspect this would be a feature that > would be of interest to others. > > The only reason it hasn't been built yet is basically that it hasn't been > donated or prioritized as highly as other features. Features get added to > DSpace through two main paths... > > 1. Either an institution builds the feature (or hires a service > provider to build it) and donates it back to DSpace (in order to benefit > the entire community) > 2. Or, our DSpace Steering group finds a way to fund the feature > (usually via community fundraising) and hires a service provider to build > it on behalf the entire community > > We do not have a centralized development team, so DSpace is very much a > global collaboration. If this feature is of high interest to you, we'd > welcome you to consider contributing it back or potentially hiring a service > provider <https://dspace.lyrasis.org/rsp/> to do so. The DSpace Steering > Group will also be discussing priorities for the 8.0 release in the coming > weeks/months. It's always possible this will come up then.. but as you > might imagine, there can be a large number of wishful features, and I don't > yet know where this one would fall on the priority list. > > Tim > > ------------------------------ > *From:* [email protected] < > [email protected]> on behalf of Stephen Brush < > [email protected]> > *Sent:* Thursday, March 2, 2023 9:11 AM > *To:* DSpace Community <[email protected]> > *Subject:* [dspace-community] Audit trail > > Hi, > > We are curious if there is any support or extensions for audit related > features, such as tracking the creator/date of new items and perhaps also > the user related to modified records. > > The only field I located in the DB was the last_modified date on the Item > table. The only thread I came across referred to v1.5. > > A separate but related ask is in the case of admins making security > related updates this could also include what the changes were. > > If audit features not implemented is there any reason other than it may > not a popular need? > > Thanks, > > Steve > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-community/22c554e7-08c6-4c95-9202-08d9609a0e9an%40googlegroups.com > <https://groups.google.com/d/msgid/dspace-community/22c554e7-08c6-4c95-9202-08d9609a0e9an%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-community/PH0PR22MB32747BA71C73970F038C84AEEDB29%40PH0PR22MB3274.namprd22.prod.outlook.com > <https://groups.google.com/d/msgid/dspace-community/PH0PR22MB32747BA71C73970F038C84AEEDB29%40PH0PR22MB3274.namprd22.prod.outlook.com?utm_medium=email&utm_source=footer> > . > -- Dr Andrea Schweer (she/her) Research Technologies Manager Information Technology Services Ph: +64 7 837 9253 University of Waikato | Private Bag 3105 Kirikiriroa Hamilton 3240 | Aotearoa New Zealand waikato.ac.nz [image: University of Waikato] *Please note that my work week is Tuesday to Friday.* *The content of this email is confidential and intended for the recipient specified in message only, unless otherwise stated.* -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/CAEyLpBqUEYO5O_EuN8A6qgawDYt6k-jKRtbVYt6zhpN-yHOVdw%40mail.gmail.com.
