Just to clarify, when you say "compound objects" you're not referring to a complex single-object model (i.e. single object with many datastreams) but actually to a multi-object model (many object linked via RELS-EXT), right?
It's usually the former that is referred to as complex and the latter as atomistic, see: https://wiki.duraspace.org/display/FEDORA35/Content+Model+Architecture FWIW, I usually prefer asserting part/membership relations in the child rather than parent object. If you have the Resource Index available, it's straightforward to query the relevant relationships for export. On 22 Sep 2011, at 6:16 AM, Kyle Banerjee wrote: > Thanks for the info -- I'm pretty new to this, so I still get tripped up on > fairly basic stuff. > > In a nutshell, the functional problem I'm trying to solve is to provide a > structure that will allow for reasonable navigation, be easy to administer, > and store data in a way that allows sensible export of the relationships. > > Am I understanding correctly that the best approach would be to point > downwards at the component objects with RELS-EXT (i.e. I should not point up > or add other objects as that just introduces confusion)? The fact that this > file could be huge is not a problem for us if it doesn't cause systems issues > as our process for generating and attaching the file will be fully automated. > Early curl experiments seem to be going really well. > > Thanks, > > kyle > > > On Wed, Sep 21, 2011 at 2:05 PM, Benjamin Armintor <armin...@gmail.com> wrote: > Kyle: > Broadly speaking, there are two ways to model this: By having the > items include a relationship pointing to the collection object, and > vice-versa. Both approaches have benefits and drawbacks: Pointing > from the item up makes transactions more straightforward, since you > are typically modifying only a single object in Fedora, but makes > building up the compound object more difficult, since you have to take > recourse to some type of index (eg the resource index). Pointing from > the collection down makes it easier to build up the compound object, > but increase both the number of objects in some transactions (you must > update the item and the collection) and the number of operations (as > the collection builds up a very large RELS-EXT). > > Adding an additional party in the form of a separate object containing > the relating data seems like it takes the worst from both of these > approaches. It's justifiable of you need to build into it more than a > simple membership pointer, but otherwise seems like a needless > complication to me. > > - Ben > > On Wed, Sep 21, 2011 at 4:44 PM, Kyle Banerjee <baner...@uoregon.edu> wrote: > > Howdy all, > > > > I need to migrate a significant number of compound objects. Some compound > > objects may contain thousands of individual items. The metadata for the > > individual items contains no reference to the parent. This means that > > inserting a relationship statement to the effect of isMemberOfCollection is > > awkward. > > > > However, I have a separate file that contains all the relationship > > information. What I'd like to do is load that as its own object as it can > > simply point to all the items, and then ingest some kind of statement that > > expresses this relationship after the parent and child objects have already > > been loaded. Is my approach possible (or even desirable), and if so, how > > would I express the relationship in FOXML? > > > > In a worst case scenario, I can combine data from the metadata and the file > > that contains the relationship information. However, I'm trying to avoid > > that if possible to make the process cleaner. Any ideas would be greatly > > appreciated. Thanks, > > > > kyle > > > > > > -- > > ---------------------------------------------------------- > > Kyle Banerjee > > Digital Services Program Manager > > Orbis Cascade Alliance > > baner...@uoregon.edu / 503.877.9773 > > > > ------------------------------------------------------------------------------ > > All the data continuously generated in your IT infrastructure contains a > > definitive record of customers, application performance, security > > threats, fraudulent activity and more. Splunk takes this data and makes > > sense of it. Business sense. IT sense. Common sense. > > http://p.sf.net/sfu/splunk-d2dcopy1 > > _______________________________________________ > > Fedora-commons-users mailing list > > Fedora-commons-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/fedora-commons-users > > > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Fedora-commons-users mailing list > Fedora-commons-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fedora-commons-users > > > > -- > ---------------------------------------------------------- > Kyle Banerjee > Digital Services Program Manager > Orbis Cascade Alliance > baner...@uoregon.edu / 503.877.9773 > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1_______________________________________________ > Fedora-commons-users mailing list > Fedora-commons-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
