Product Name: CMFBibliographyAT

Description

From: http://plone.org/products/cmfbibliographyat

CMFBibliography enables the handling of references to various types of (scientific) publications. In order to allow for interoperability with other applications that support reference handling, the information within individual references is highly structured. The concrete schema used depends on the kind of publication one wants to make reference to, so there is a variety of different reference types to choose from. The overall schema design follows closely BibTeX's approach, a very flexible and powerfull reference management system that comes with LaTeX.

It provides a Bibliography Folder content type dedicated to holding reference objects of various kinds, like for articles, books, preprints, techreports, contributions to collections, ... The folder supports import/export of BibTeX formated files per default and additional formats depending on configuration.

In addition the package adds a bibliography action to the portal tabs and it provides a BibliographyTool called portal_bibliography through which you can manage the renderers and parsers for the import/export functionality (in ZMI).

Excerpt from email from R.Ritz on 6 July 2006

Well, as of now, CMFBib's development hasn't been as formalized as for bigger projects like Plone itself given its realivily small user base. But this is currently about to change (the user base I mean) so it might be indeed about the time to become more explicit and transparent here for CMFBib as well. Rest assured that there are several major projects which use CMFBib in production (some since years) ...

The current road map (if it can be called like that at all) is to finish the proper integration of duplicate handling on mass uploads (some migration/backwards compatibility issues still have to be fixed) before releasing an 0.9 version and then focusing the development on adopting Zope 3 style coding patterns. There is no concrete time line but the hope is that people might be able to allocate some time during the summer break for that.

Excerpt from email from R.Ritz on 7 July 2006

CMFBib itself is mostly about providing the core for handling bibliographic data within Plone: content types; import/export support; a transformation for the transforms tool to make the reference data easily accessible from within any text field (aka via \cite{bibkey} and \bibitem{bibkey}).

How you use CMFBib within your site is rather a matter of site configuration and policy. One usage pattern that turns out to be appropriate for many applications is to collect the bibliographic data all in one large bibliographic folder (the BTree based one) and to manage individual lists (a group or persons list of publication; suggested readings for a course; citations of a certain piece of work, etc) either by ATBiblioList if they are static or by ATBiblioTopic if they are dynamic (no release yet but you'll find it in the collective).

Also, if you are just getting started I strongly suggest you look at trunk (not the 0.8 release). trunk is close to the forthcoming 0.9 release and the backwards compatibility issues that need to be fixed before won't affect you anyway.

The product's principal developers include:

• Raphael Ritz (r . ritz biologie hu-berlin de)

On-line Resources

Home page

• http://plone.org/products/cmfbibliographyat, including links to documentation, releases, a roadmap, an issue tracker and the project's code repository (in the PloneCollective?)

Mailing list

• Info: https://zaubberer.net/mailman/listinfo/plone-biblio
• Post: plone-biblio@zaubberer.net

Example implementations

• http://www.bccn-berlin.de/
• http://bccn.neuroinf.de/
• http://www.ecology.uni-kiel.de/ecology/site/departments-en/za/publications-za (demonstrating the ATBiblioTopic)
• http://www.simula.no/pubs (adapted and set up by PloneSolutions?)
• http://www.naturalsciences.be/
• http://mis.ucd.ie/research/bibliography_view

How-tos and Tutorials

• http://mis.ucd.ie/wiki/CMFBibliographyAT (How to use CMFBibliographyAT as implemented by the UCD School of Business in Dublin)

Dependencies (i.e., other products required)

• ATExtensions

Extensions/AddOns

• ATBiblioList
• ATBiblioTopic
• BibCentral
• BibExporter
• BibFactoryFix
• BibLexis
• BibLoc
• BibNavi
• BibNotes
• BibRefScraper
• BibteXMLBiblio
• IngentaRefs
• LinguisticReference
• MarsBibliography
• RefBiblioParser

Status of Evaluation

In progress (12 July 2006; TomElliott).

• 12 July 2006
  • Successfully installed/uninstalled both release 0.8 and svn trunc latest in Plone 2.5 (windows)
  • Initial impressions (based primarily on playing with product in Plone, minimal code look):
    • Pro: working code!
    • Pro: bibliography tab (aggregation point) is nice
    • Pro: friendly, responsive developers (both on-list and in private correspondence)
    • Con: Only one title per work? What about translations, short titles, abbreviations?
    • Con: author fields embedded in content? What about authority control?
      • Editor toggle affects all authors simultaneously. What about other types of creator, e.g., translator
    • Con: inJournal: reference to parent journal is by "standard abbreviation", with no authority record or other control/assist
    • Con: inCollection: reference to parent work is encapsulated in the child object? What happens if you want to cite multiple articles from the same parent collection? Do you have to enter this data multiple times?
    • Query: why not use relationships for parent-child work relations?