Dear all,
I'm using D7 to build a catalog rerefencing books available in different libraries and in different formats (Audio, Digital text, Braille...).
To achieve this I define a content type for bibliographic recors. It has fields for title, author, ISBN, book description. And also I consider using the composed_field module to define an item filed. So a bibliographic record will have as many item fields as there are available books in different libraries. Each item filed should include at least the type of item, (Braille, audio, etc.), the library that owns it and a link for getting more information.
My question is: how best describing libraries in Drupal? Ideally one shold be able to use a library name as a taxonomy field (clicking on it will show all the books for which the library has at least one item of that book). But one may also want to associate othe rinformation to a library. At the minimum a link to its website, but perhaps also aphysical address, a phone number, perhaps even freeform text info, so that would suggest to create a dedicated content type for libraries but then I suspect that the benefits of taxonomy fields would be lost.
Any comment on how to best represent libraries in particular but also on the general architecture described above would be warmly appreciated.
Thanks a lot in advance! Shérab.
Don't try to reinvent libraries! They have been doing it for centuries. Logon to the catalog at your local public library and see what they do. There are only a handful of companies that produce the software for all the library catalogs. It is a very tough job to compete with their resources. I once tried to put our non-profits library catalog online on our website. I gave up and used Library Thing as a third party solution. .
On Tue, Dec 31, 2013 at 5:29 AM, Shérab Sebastien.Hinderer@ens-lyon.orgwrote:
Dear all,
I'm using D7 to build a catalog rerefencing books available in different libraries and in different formats (Audio, Digital text, Braille...).
To achieve this I define a content type for bibliographic recors. It has fields for title, author, ISBN, book description. And also I consider using the composed_field module to define an item filed. So a bibliographic record will have as many item fields as there are available books in different libraries. Each item filed should include at least the type of item, (Braille, audio, etc.), the library that owns it and a link for getting more information.
My question is: how best describing libraries in Drupal? Ideally one shold be able to use a library name as a taxonomy field (clicking on it will show all the books for which the library has at least one item of that book). But one may also want to associate othe rinformation to a library. At the minimum a link to its website, but perhaps also aphysical address, a phone number, perhaps even freeform text info, so that would suggest to create a dedicated content type for libraries but then I suspect that the benefits of taxonomy fields would be lost.
Any comment on how to best represent libraries in particular but also on the general architecture described above would be warmly appreciated.
Thanks a lot in advance! Shérab. -- [ Drupal support list | http://lists.drupal.org/ ]
Walt Daniels (2013/12/31 10:37 -0500):
Don't try to reinvent libraries! They have been doing it for centuries.
Yes I know about ILMS. I used Koha rather intensively. So it's a conscious decision to do it in Drupal.
But I think one could almost forget about liraries in the question, which was really a content-type vs. taxonomy issue. But now with entities in D7 and the ability to add fields to anything I think it's best to use a taxonomy to represent ieach library.
Best wishes and thanks, Sherab.
Take a look at the relations module.
On Dec 31, 2013, at 8:00 AM, Shérab Sebastien.Hinderer@ens-lyon.org wrote:
Walt Daniels (2013/12/31 10:37 -0500):
Don't try to reinvent libraries! They have been doing it for centuries.
Yes I know about ILMS. I used Koha rather intensively. So it's a conscious decision to do it in Drupal.
But I think one could almost forget about liraries in the question, which was really a content-type vs. taxonomy issue. But now with entities in D7 and the ability to add fields to anything I think it's best to use a taxonomy to represent ieach library.
Best wishes and thanks, Sherab. -- [ Drupal support list | http://lists.drupal.org/ ]
-
Shérab -
Walt Daniels -
Warren Keuffel