I'm charged with digitizing some older periodicals and providing user content to them. Since a Drupal site is already in place for the archival institution, I need to work within its parameters. I'm trying to come up with a logical relationship structure to catalog and provide access to the content. Here's a scenario:
A periodical, let's called it History Monthly, is published with a volume and issue number (e.g., Vol. 6, No. 8). It has a publication date and certain other issue-level metadata that I need to account for. Contained within each issue is a dozen articles, with their own bits of information (e.g., author, contents, images, subject), etc.
Is there a way to create some sort of node or entity hierarchy so that articles are organized under an issue, and issues under a series. So...
At the top most level is the periodical name (History Monthly). Volume numbers would be children of the periodical level, issue numbers would be children of each volume, and articles would be children of each issue number, etc. An author list would exist independently of this hierarchy, though it would need to be entered at the article level.
I'm hoping to keep redundant data entry to a minimum, e.g., having to enter volume and issue numbers to each article rather than, say, being able to drag and drop issues under their parent volumes and articles under their parent issues. If drag-and-drop isn't a possibility, what sort of arrangement alternative is there to allow for inheritance and neat classification?
Is any of this even possible--or desirable? I'm not sure how to create this sort of hierarchical relationship with Drupal, nor necessarily what sort of content type, say, an issue becomes (can't just be a number since each issue would have associated metadata). I looked into the book module but it doesn't seem sufficient.