Dear list, I'm currently working on my PhD project, where I'm building a distributed archiving solution.
Basically the distributed archive will consist of a number of nodes (every node belonging to another organization), where every node will be storing his data on a local node and replicas on a number of selected remote nodes. There will be a number of predefined processes (eg., integrity checking, creating additional replicas, etc.) that will run either periodically or when some event occurs (node lost event, corrupted object event, etc.). The data that the system will archive will consist of RDF/XML files (metadata) + binary files (e.g., tiff images, jpeg images, etc.; referenced from the RDF). The RDF/XML files together with the binary files will be the products (in OODT language). I'm looking into OODT to see if it can be used to create such a system and what components I would be using. In the following is a list of components that I have identified that I could use: - CAS Workflow (to implement the processes) - CAS Push/Pull Component (to send products to remote nodes, to get products from remote nodes). With what is the push/pull component communication on the other side? The push/pull component? From where is the push/pull component getting the data that it will send? From the file manager? What I'm missing, but should be there somewhere: - Security Component. How do I create Virtual Organizations and manage user and groups, so that I can restrict access? Probably also needed: - File Manager. In my case I would have the products (rdf + binary files) and would need to create the profiles on the fly with some basic information. Do I need the file manager for something other than for the end user to access products and profiles? Since I'm going to load up the RDF files in a triple store for further use, is it possible to extend the file manager so that the profile catalog is stored in a triple store? Thank you very much for you time :-) Best regards, Ivan
