Closed briri closed 6 years ago
I think option 3 is the easiest to implement. Agreed about the separate repository though.
Two comments:
@sjDCC and @stephaniesimms is this still relevant now?
nope. we should close this and discuss if this is ever something we want to be able to do in light of dmponline subscription.
It would be valuable for a new publicly accessible DMP to be available across all of the installations of DMP Roadmap (e.g. DMPTool, DMP Online's, DMP Tuuli, DMP Assistant, etc.).
There are several ways to handle this (and perhaps others I'm not seeing):
A list of installations could be maintained and an API developed that provides public DMP template data (as JSON). A scheduled rake task could then be run that runs through the list of installations and calls their API to retrieve the latest plans (ActiveJob is a good candidate for this).
Someone or a group of people can be assigned to manage the list of public DMP templates in an online repository. A mechanism could then be built to retrieve public DMP templates from this location rather than the local database. The information could perhaps be made accessible via an RSS feed or JSON/XML. Submissions of new templates would need to be made to the designated maintainers of the list.
We could begin storing publicly accessible DMP templates as files and allow them to become part of the Git repository. Then each time a plan is made public the institution could submit a Pull Request and once merged a notification can be sent out to all of the repositories watchers asking them to pull down the new template. This option could get messy though ... perhaps best managed in a separate repository.