Posted by milos.kroulik on April 17, 2009 at 3:21pm
Jump to:
| Project: | Library |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I would use some bibliographical fields for each copy (for example publisher, date of publication...) I really don't know, if it's good idea to implement it this way, though. I think the way can be rework of library module, so each copy would correspond to node (so we coould use CCK) and will be automatically linked to other copies by means of nodereferenceThe the only task for library module would be to create node with circulation interface.
Comments
#1
Sadly, this would be a huge change. You could implement this yourself with the module as it currently is by creating a content type called 'library item' and only ever allowing one copy per node. Each library item could have whatever fields you wanted it to. Then, you could create parent content types that grouped the library item content type using nodereference like you mentioned.
#2
What about using the biblio module in conjunction with library? That's what I'm in the process of doing. However, you would have to make a new node for each copy and then tag the node with a taxonomy listing of some type instead of adding additional copies within a node. That might be a path to compatibility and future use of different modules also.
#3
Right - that's kinda what I was suggesting. The library module works with any content type, so if the biblio module creates one, you could just as easily enable library functionality on that type.