I'm looking into using the Atomistic Model with my collections.
I'm trying to find the best way to connect the parent objects to their child
objects. I've set up queries similar to those in collection objects which
would work well for the currently collections I'm working with. However, some
of the later collections I'll be working with are larger and creating queries
for the parent objects just isn't feasible. I was wondering if others would be
willing to share how they set up their relationships and Content Model
Architecture?
The collections I'm currently working with are non-archival and usually only
have one to three child objects, so I'm also wondering if it's even worth it to
use the Atomistic Model or if I would be better off with the Compound.
Thanks for your time,
Barbara
Barbara Yates Hilderbrand, MLS
Metadata/Digital Collections Librarian, Library Associates
NASA/GSFC Library
Code 272, Building 21
Greenbelt, MD 20771
301-286-6246
[email protected]
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Fedora-commons-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
