What happens to references to duplicate files stored in an online backup directory, as well as ones stored in a remote backup location? In more complicated versions of this question, how would a federated archive handle replicas stored in other archives?
Then, would it matter if the archive decided to do a slight reformat of the data that merely rearranged the numerical values without adding or deleting any of them? Bruce B. On Wed, Apr 22, 2015 at 6:09 AM, Thomas Bennett <[email protected]> wrote: > Hi, > > Okay - so a 'flat' product has a single datastore reference. > > So, how do you handle redundant copies of products? At the moment I have an > independent catalogue at each site. > > I was thinking of a site metadata key, so multiple products can be > filtered, but I thought I would see what other people are doing and if > there is any interest in perhaps getting a product (flat or heirachical) > with multiple references, i.e. beyond originalReference and > datastoreReference. > > Or does that totally break the OODT model? It probably does... > > Also - does anyone store data on tape library and index it with OODT. I'm > talking basic tar on a tape. This obviously breaks the file retrieval, if > used, but I'm thinking of how this could be included in the OODT framework > and maybe develop some methods. > > But before I go to deep I thought I would ask. > > Cheers, > Tom >
