cancel
Showing results for 
Search instead for 
Did you mean: 

Implementing bibliographic content - aspect, type?

rtl
Champ in-the-making
Champ in-the-making
I'm looking to implement support for capturing bibliographic data in Alfresco as part of a knowledge repository with an aim of outputting bibtex in a custom template (as for RSS). I would appreciate some feedback on the best way to achieve this.

Initially, I'd thought that this was a natural use of aspects, allowing a bibliographic aspect to be added to any content in the repository. But, there are more than 10 different types of bibliographic entry, each with their own optional/mandatory set of fields. Which is doable with aspects, but starts to fill up the aspect dropdown fairly quickly.

Another approach is to use a basic bibliographic content type (holding the common fields) with aspects that specialise the base type having the properties specific to the type of bibliographic entry required (journal, phdthesis, book, etc). This new type would allow child types, such as binary for uploading copies of publications (pdf, docs, etc).

A third approach might be to use a content type that manages all the sub-types internally, dynamically changing the set of properties depending on the bibliographic type required - but I don't see any support in Alfresco for dynamic properties.

I suppose what it boils down to is what is the preferred/best way to implement content with a larger number of abstract/concrete or sub-type/super-type relationships?
1 REPLY 1

osu
Champ in-the-making
Champ in-the-making
Hi,

Did you come to a conclusion on that?

Regards,
Oliver.