EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #09540
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Default import plugin
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Default import plugin
- From: "Alan.Stiles [He/Him/They]" <alan.stiles@open.ac.uk>
- Date: Thu, 18 Jan 2024 10:57:07 +0000
CAUTION: This e-mail originated outside the University of Southampton.
Hi all, I’m trying to remove old customisations where the current core code now performs similar functions. One of the things is a custom version of the Screen::Import::render_import_bar to set a default plugin using a config value, where it appears
TMB added a similar function to core, as seen in In order to set that “default_import_plugin” parameter, am I right in thinking I’d still need to have a customised Screen::Items plugin to call (something like) “render_import_bar( default_import_plugin=’DOI’); “ or have I completely
overthought it? Thanks, Alan Alan Stiles (he/him), Digital Repository Developer oro.open.ac.uk |
- Follow-Ups:
- RE: [EP-tech] Default import plugin
- From: John Salter <J.Salter@leeds.ac.uk>
- RE: [EP-tech] Default import plugin
- Prev by Date: Re: [EP-tech] Internal Server error 500 opening view items, Saved searches and Users + Error in Script
- Next by Date: RE: [EP-tech] Default import plugin
- Previous by thread: [EP-tech] Ubuntu 20 or 22 LTS
- Next by thread: RE: [EP-tech] Default import plugin
- Index(es):