@simonmitternacht wrote:
I am testing whether OMP could be used for handling PhD thesis submissions at my university. One of the features we would need to add is support for embargo times on certain objects. At submission the user should be able choose to add an embargo time for their thesis (or possibly for each chapter/file). Later, when the thesis is cleared for publication it should appear as a title in the catalog, but access to all or some of the files should be blocked until the embargo period is over.
As an experiment, I have made a crude implementation for adding submission embargoes here: https://github.com/ubbdst/omp. That solution has several problems, I have to alter core tables and a large number of classes to make sure the embargo is respected and propagated throughout the site (and I probably missed some places). But, I have struggled trying to separate it. If I store the embargo times in a separate table I run into problems with submissions not being assigned ID's before the end of the submission wizard (if I understood it correctly?). If I attach embargoes to files instead of submissions, I am afraid there will be some complicated book-keeping in propagating the embargo over several revisions (one option could be to only add embargoes before production). I also tried creating a plugin, but ran into two additional problems: some of the steps where I need to extend behavior don't have hooks (which seems straight-forward to solve), and I need to modify some of the templates for the submission wizard and frontend/catalog (which seems difficult?).
So, my question is, is the first approach the best, in spite of it meddling with a lot of core functionality, or is there a more modular/isolated approach that you could suggest? Also, would there be interest in adding this as an optional feature of OMP/PKP?
Posts: 4
Participants: 3