EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #10278

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] EPrints outward-facing changelog

CAUTION: This e-mail originated outside the University of Southampton.
Hi

I'm working with an EPrints 3.4.7 repository for a construction management research metadata catalogue (non-profit). There is more to it than a catalogue; I have also developed taxonomic structures for indexing and searching 
/browsing. I'd like to implement a systematic way to track and publicly display:

1. User suggestions and feedback we receive
2. Our responses and decisions about those suggestions
3. Changes made to the repository with rationale
4. Implementation tracking with dates and affected components

Desired tracking fields:

· Suggestion origin/source (user email, internal, etc.)
· Dates (received, implemented)
· Suggestion text and our response/explanation
· Status (received, under review, implemented, rejected)
· Files/features affected
· Expected vs. actual outcomes

I'm considering creating: A new EPrint-type "changelog" or extending existing types with additional metadata fields to manage this process within EPrints itself.

Before building from scratch, I'm wondering:

· Has anyone implemented similar change tracking or public suggestion management in EPrints?
· Are there existing plugins or Bazaar packages for changelog functionality? ( I searched to no avail)
· Any recommended approaches or lessons learned from similar implementations?

The goal is transparency with our research community while maintaining a structured internal process for repository evolution.

Thank you for any suggestions or pointers!

Best wishes 

Will Hughes
____