<div dir="ltr">Hi Ian,<div><br></div><div>thanks for the answer.</div><div><br></div><div>What if one did this the other way round, i.e. institution-wide repository, and then do something on a departmental server to provide listings for that department? </div><div><br></div><div>Thanks!</div><div>Bjoern</div><div><br></div><div><div class="gmail_extra"><br><div class="gmail_quote">On 3 April 2015 at 16:03, Ian Stuart <span dir="ltr"><<a href="mailto:Ian.Stuart@ed.ac.uk" target="_blank">Ian.Stuart@ed.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I understand what you are trying to do.... and, in theory, it's a good idea.<br>
<br>
If the departmental eprints were standard (unmodified) systems, then<br>
each one can export records in the EPrint-XML format, and that will be<br>
the same for all repositories.... and thus compatible with the main<br>
Institution-level one.<br>
<br>
Where things start to fall down is when repositories become modified....<br>
and I don't mean in the templates and the way the web pages are<br>
displayed - I mean in the contents stored for each record:<br>
<br>
If one department classifies articles by research group, and another by<br>
subject classification, then you can't merge them.<br>
<div><div class="h5"><br>
<br>
<br>
On 03/04/15 14:55, Bjoern Hassler wrote:<br>
> Hi all,<br>
><br>
> I've got a newbie question, apologies if it's obvious.<br>
><br>
> Is anybody in this situation: Several eprints instances within an<br>
> institutiton (e.g. at departmental level), with an overall institutional<br>
> level repository (populated entirely through OAI Harvester or otherwise)?<br>
><br>
> Is this essentially supported out of the box by installing an<br>
> institution-level eprints instance, and letting it harvest the<br>
> departmental level instances?<br>
><br>
> From a users perspective, is the functionality is the same (i.e.<br>
> equally smooth, same look and feel, etc)? I.e. is there a difference<br>
> between "native" records (say departmental level) and "harvested"<br>
> records (institutional level), from the users perspective? By "user" I<br>
> mean the person browsing the repository ("anonymously") on the web -<br>
> obviously there's a difference from the contributors perspective.<br>
><br>
> Does it make sense for the institutional repository to harvest<br>
> departmental repositories? Or would it be preferable to have a single<br>
> institutional repository and generate listings for departments from it<br>
> (which should be viewable within the sub-domain owned by the<br>
> department)? If the latter is preferable, what would be the simplest way<br>
> of doing that? (Set up departmental repository, and let it harvest the<br>
> institutional one? Or are there other e.g. API-based options?)<br>
<br>
<br>
</div></div>--<br>
<br>
Ian Stuart.<br>
Developer: ORI, RJ-Broker, and OpenDepot.org<br>
Bibliographics and Multimedia Service Delivery team,<br>
EDINA,<br>
The University of Edinburgh.<br>
<br>
<a href="http://edina.ac.uk/" target="_blank">http://edina.ac.uk/</a><br>
<br>
This email was sent via the University of Edinburgh.<br>
<br>
The University of Edinburgh is a charitable body, registered in<br>
Scotland, with registration number SC005336.<br>
<br>
*** Options: <a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech" target="_blank">http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech</a><br>
*** Archive: <a href="http://www.eprints.org/tech.php/" target="_blank">http://www.eprints.org/tech.php/</a><br>
*** EPrints community wiki: <a href="http://wiki.eprints.org/" target="_blank">http://wiki.eprints.org/</a><br>
*** EPrints developers Forum: <a href="http://forum.eprints.org/" target="_blank">http://forum.eprints.org/</a><br>
</blockquote></div><br></div></div></div>