Registry Interface Working Draft Discussion Topic

Should we add a harvestFrom attribute to the VOResource schema?

Both the STScI registry and Carnivore use an internal atribute called harvestFrom to track where they get records from. This could be useful to expose when investigating problems in the record contents.

There is another way to determine a record's origin based on its authority ID which involves searching for the Registry record that claims management of that ID. However, this is not necessarily the same as where a registry harvested the record from (though it is in practice to day). In addition to addressing this ambiguity, a harvestFrom attribute attached to the record itself is easier to get.

Since this piece of metadata is not originate from the resource provider, but really describes the registry that manages the record, it would be encoded as an XML attribute of the Resource element.


If you have an opinion, question, or comment about this topic, feel free to append your discussion below. Be sure to indicate your name as the author.




Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2005-03-30 - RayPlante
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback