Voting starts in March for the Drupal Association Board election.
G'Day and thanks again for a great module.
In several of my applications, we have a biblio installation provided to users of an secure collaboration site. So these collections of citations grow and grow quite nicely...then one day the Communications people note that they would really like to provide public access to the Biblio collection, in their public theme, and without people needing to login.
Option1: Periodically replicate the Biblio database to the public website
- Biblio does not seem to support a comprehensive export that I can see. We have several CCK fields added to the Biblio type to link biblio nodes into the rest of the system (imagine need to see a list of publications filtered on an internal project number). So any export from Bilbio would need to scoop up all the cck fields as well...and on the other side, an import agent would need to likewise handle both Biblio's structures as well as the cck values.
Option2: Figure out how to segment the biblio collection on the extranet using nodeaccess or other Drupal ACL modules
- Possible, but not desireable because the ACL modules are complicated, fiddly, and don;t always play well with Biblio. (I have nodeaccess grants denying public view of biblio right now, and biblio happily reveals itself anyway)
Option 3: The subject line of this query...see if there's a way to open up a webservices interface to the Biblio collection so that the public site can offer a search interface.
Any thoughts greatly appreciated. I'm also happy to consider paid engagement for bona fide bilbio gurus!