EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #04889
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: Bazaar Improvements
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Re: Bazaar Improvements
- From: "Alan.Stiles" <alan.stiles@open.ac.uk>
- Date: Thu, 8 Oct 2015 16:01:37 +0000
I like the principle of it - I don't think listing the repositories would be a major security risk as, if you were sufficiently determined, it would be feasible to go and check each repo from ROAR to see if it had that plugin installed (or write a script, much like you have, to do it). Security through obscurity is no security at all - or however that saying goes. It might also be helpful to show which versions of eprints the plugin is running on, so you know if it works on what you've got before you try it, and potentially whether it is actually a requirement on your version of eprints. E.g. my CheckDOI plugin which, *I think*, has been built in to core eprints since 3.3.13 so serves no purpose for up to date repositories. Alan -----Original Message----- From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Field A.N. Sent: 08 October 2015 16:41 To: eprints-tech@ecs.soton.ac.uk Subject: [EP-tech] Bazaar Improvements I've scripted a process that will check which bazaar packages are installed on repositories registered in ROAR ( roar.eprints.org -- you should register your repository there if you haven't already). This means that when you're considering installing a package, you can easily identify the ones that your peers already have (meaning you can ask for help). I've also created a page where you can see all items, listed by popularity: http://bazaar.eprints.org/all_by_popularity.html If you click through to an item, you can see the number of instances detected on the abstract page. If anyone has any suggestions or ideas on how to improve this, please let me know. There was a suggestion of listing the repositories that had the package installed on it so that people could discover *who* was using packages, but others argued that this might be a security risk. What are the community's thoughts on this? -- Adam Field Business Relationship Manager and Community Lead EPrints Services +44 (0)23 8059 8814 *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech *** Archive: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/ *** EPrints developers Forum: http://forum.eprints.org/ -- The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302). The Open University is authorised and regulated by the Financial Conduct Authority.
- References:
- [EP-tech] Bazaar Improvements
- From: "Field A.N." <af05v@ecs.soton.ac.uk>
- [EP-tech] Bazaar Improvements
- Prev by Date: [EP-tech] Re: Regenerate Views from Admin page causes [pin missing: orcid]
- Next by Date: [EP-tech] Re: Bazaar Improvements
- Previous by thread: [EP-tech] Bazaar Improvements
- Next by thread: [EP-tech] Re: Bazaar Improvements
- Index(es):