EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #09774
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] "Configuring Distinct Input Forms for Multiple Archives in Shared Hosting Setup"
- To: <eprints-tech@ecs.soton.ac.uk>
- Subject: Re: [EP-tech] "Configuring Distinct Input Forms for Multiple Archives in Shared Hosting Setup"
- From: Florian Heß <hess@ub.uni-heidelberg.de>
- Date: Wed, 24 Jul 2024 09:21:00 +0200
CAUTION: This e-mail originated outside the University of Southampton. Hi Sudharsan What you describe I am afraid calls for all kind of hassles we already experienced and got rid off (mostly). Maybe I can offer some impulse concerning how we finally managed a common configuration base of our E-Prints repositories, and to store derivations for specific instances at a single place, versioned by git or whatever. You would need: - A git or whatever dcvs repository for all configuration - A convention of your choice about an additional secondary ending of the filenames in your config git/* repository e.g.: *.X -> apply to all repositories *.S -> apply to subject-related repositories, to exclude a given repository H in our case *.H -> EPrints repository for our students and university members *.A -> subject-specific EPrints repository about the Arts *.P -> subject-specific EPrints repository about, say, Philosophy *.C -> subject-specific EPrints repository about, say, Classical Studies - A management script that when run links and rearranges links to these files to the according places (inferred from the path levels in the config reposotory) in the directories of the repository/-ies they apply to. That script should observe and handle situations that need closer care, say if you exchanged a link to a proper file for epiphemeral tests later on. - because the target files are links, you would need to re-run the script only when files are added or the suffix of a file changes. After changes to common files, you might need to issue epadmin commands for every repository concerned. - occasionally a configuration for the management script for finer control, e.g. to handle your derivations of files without suffix beyond the repository-specific stuff. It works pretty well for us, but I do not know how it adapts best to your own situation. I can provide only hints for you to ponder further over. But to try to answer your very question: The cfg.d directory is what I think you need to derive for each repository. Try not to touch pub_lib, as changes therein may be reset on updates. Regards Florian Hess Am 24.07.24 um 08:28 schrieb Techsupport Mosys:
*CAUTION:* This e-mail originated outside the University of Southampton. *CAUTION:* This e-mail originated outside the University of Southampton. Dear Team, We have a base installation (version 3.4.4) and aim to set up multiple archives. For instance, we plan to offer shared hosting services to various organizations. We've installed 5 different archives but noticed that all the archives share the same input forms for adding items. We need distinct input forms for each archive. What files need to be copied, and what configuration changes should be made in the archives folder to achieve this? Thanks Sudharsan *** Options: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2Fw%2FEprints-tech_Mailing_List&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7Ce5e69cfb49724edf5e6208dcabb13200%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638574024734838237%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=TYGe6R6UoPpdQN5ddI4hTmVPQ99mYVOIsumV5XLdHXc%3D&reserved=0 *** Archive: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7Ce5e69cfb49724edf5e6208dcabb13200%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638574024734838237%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=uIO6OSQ%2FXpywax1bBAStEVQLnwvg9iahVmFWztaOQfI%3D&reserved=0 *** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.eprints.org%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7Ce5e69cfb49724edf5e6208dcabb13200%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638574024734838237%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=hWri2B%2B2Wc4amD%2FHPnMP7LUFjIFoDxMu0pjZPThkTtU%3D&reserved=0
-- UB Heidelberg (Altstadt) Plöck 107-109, 69117 HD Abt. Informationstechnik https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ub.uni-heidelberg.de%2F&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7Ce5e69cfb49724edf5e6208dcabb13200%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638574024734838237%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=%2BfxeUehbIJZuI%2BMYFwcDIL5PWCfO728JwyOOIMt4%2F%2BE%3D&reserved=0
- Follow-Ups:
- Re: [EP-tech] "Configuring Distinct Input Forms for Multiple Archives in Shared Hosting Setup"
- From: Techsupport Mosys <techsupport@mosys.org>
- Re: [EP-tech] "Configuring Distinct Input Forms for Multiple Archives in Shared Hosting Setup"
- References:
- [EP-tech] "Configuring Distinct Input Forms for Multiple Archives in Shared Hosting Setup"
- From: Techsupport Mosys <techsupport@mosys.org>
- [EP-tech] "Configuring Distinct Input Forms for Multiple Archives in Shared Hosting Setup"
- Prev by Date: [EP-tech] "Configuring Distinct Input Forms for Multiple Archives in Shared Hosting Setup"
- Next by Date: Re: [EP-tech] "Configuring Distinct Input Forms for Multiple Archives in Shared Hosting Setup"
- Previous by thread: [EP-tech] "Configuring Distinct Input Forms for Multiple Archives in Shared Hosting Setup"
- Next by thread: Re: [EP-tech] "Configuring Distinct Input Forms for Multiple Archives in Shared Hosting Setup"
- Index(es):