CAUTION: This e-mail originated outside the University of Southampton.

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://wiki.eprints.org/w/Eprints-tech_Mailing_List
> *** Archive: https://www.eprints.org/tech.php/
> *** EPrints community wiki: https://wiki.eprints.org/
>

--
UB Heidelberg (Altstadt)
Plöck 107-109, 69117 HD
Abt. Informationstechnik
http://www.ub.uni-heidelberg.de/
*** Options: https://wiki.eprints.org/w/Eprints-tech_Mailing_List
*** Archive: https://www.eprints.org/tech.php/
*** EPrints community wiki: https://wiki.eprints.org/