<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">HI Beth,<div><br><div>I can not directly answer your question, but I did want to let you know that Policyarchive.net is a DSpace instance with Manakin. Why not have the content deposited in both? Maybe you can even use SWORD to facilitate this. The IR being the "steward" of the content and PolicyArchive having a rich collection of subject based documents. It is also a good preservation strategy to have the same document in different geographical locations under different management regimes.</div><div><br></div><div>best, Michele</div><div><br class="webkit-block-placeholder"></div><div>Hi,<br><br>I have just run into my first case where I am finding our IR in <br>competition with a Subject Repository. I've been working with an <br>institutional center which is outside of our university but very <br>closely affiliated with it. We were about to make some final <br>decisions about community and collection development when my contact <br>discovered a new Subject Repository supporting the type of research <br>conducted at their Center and wants to explore this alternative <br>before committing to submitting their work to our university repository.<br><br><a href="http://www.policyarchive.net/index.php">http://www.policyarchive.net/index.php</a><br><br>I am wondering if others have run into this dilemma and can provide <br>me with many good reasons why submission should take place in and <br>institutional repository rather than a subject repository?<br><br>Also, as a side question, I know you can item map within your own <br>DSpace instance, but is it possible to item map to another DSpace instance?<br><br>Thanks for the feedback,<br>Beth Tillinghast<br><br></div></div></body></html>