On Wed, Nov 14, 2012 at 7:52 PM, Alain Tschanz <[email protected]> wrote: > Thank you for your quick response. An obvious solution just occurred to me. > What if I set up a second, "public" DSpace instance that mirrors the first > "private," DSpace instance, but the second DSpace site harvests from the > first, private instance only metadata and references to bitstreams and not > the bitstreams themselves?
Yes, that's possible. But I don't see what improvement it brings over my second suggestion. Let me put it another way. You need to define who you want to give access (logged in people, anonymous people, robots) to the bitstreams. Only then you can start planning a solution. Can you reply with the details of whom you'd like to have access? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
