How to create a fedora database that isn't visible to Islandora or indexed?

[Peter .]

Hi,

I would like to create a second database instance within Fedora that isn't visible to Islandora (ie it isn't viewable from the repository screen but is still accessible through the back end to apply admin functions) and is not indexed by Solr (or what have you). I am not clear on how to accomplish this so if someone could give some pointers that would be great!

Thanks.

[Nigel Banks]

I'm not sure I 100% understand what your trying to accomplish.

You'd like to create another (entirely separate) fedora repository that is not publicly accessible?

[Serhiy Polyakov]

If your target Fedora instance needs to be completely separate but on the same server you can install it in a separate Linux user home directory with separate Tomcat on a different port, for example 8081.

Serhiy

--
You received this message because you are subscribed to the Google Groups "islandora-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to islandora-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Rosemary Le Faive]

I'm doing something kind of similar - setting up multiple Islandora sites for separate namespaces within the same Fedora repository. To do this, I had to tell Islandora to limit its namespaces (in Islandora config) and tell Solr to limit its namespaces (in Solr config 7.x). 

But then even someone who was logged in as admin couldn't breach the namespace partition from within one Islandora. I'm not sure if this is what you meant by "back-end" or if you want the admin stuff to only be visible through the Fedora interface... in the first case, read on.

What else I've done is made a "Private" collection that's only accessible to logged in Drupal users. I used the XACML module to define which groups of Drupal users could view these, which thanks to XACML module magic writes to RELS-EXT, which (through a modified foxml-to-solr) gets indexed to the solr fields rels.isVisibleToUser and rels.isVisibleToRole, which go into the XACML configuration, so *bam* all solr queries through Islandora are filtered by what the current user/role can see. l'm not sure how this plays out when you do a RI query (e.g. listing the contents of a collection) so you might want to keep your admin-only Fedora objects in a separate collection or an orphan collection or no collection. 

[Peter .]

Hi Rosemary,

Thank-you for the reply. That really helped out a lot. I was thinking of using this method to separate published materials from unpublished ones (which the admins would still need access to). This sounds like a solution.