Hardy, D.R. and Schwartz, M.F. (1995). Harvest User's Manual, Technical report, February 1995, Version 1.1.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....Broker Harvest (Bowman 1995) Harvest is well represented by the above diagram (the names broker and gatherer are issued from it) A broker can be set to handle a selected vocabulary to avoid scaling problems of unfocused global indexes. Harvest uses SOIF (Summary Object Interchange Format) (Hardy Schwartz, 1995) attribute values to store the indexing information and exchange it between the gatherers and brokers. SOIF delineates streams of object summaries, and allows for multiple levels of detail. Each template (to summarise an object) contains a type, a URL, and a list of byte count delimited ....

Hardy, D.R. and Schwartz, M.F. (1995). Harvest User's Manual, Technical report, February 1995, Version 1.1.

....and processing. There are a diversity of formats for describing, storing and exchanging bibliographic information. When analyzing the demands of MyView we considered many of them, for instance MARC (library exchange format) 19] BibT E X (L A T E X bibliography format) 27] SOIF (Harvest) [12, 32], RFC 1807 (NCSTRL) 37] Dublin Core [56, 57, 53] RDF (Resource Description Framework) 43] MCF (Meta Content Framework) 20, 14] Semantic Header [21] and TEI (Text Encoding Initiative) 7, 16] Basically all formats are more or less suitable for our warehouse scheme. Only the expense for ....

....two extremes meta search engines (MetaCrawler [50] SavvySearch 21 ) and networked literature collections (NCSTRL 22 ) overcome the latter interface diversity, but problems remain: predefined search space not configurable by the user, restricted retrieval capabilities. The Harvest system [12, 32] is an integrated set of customizable tools for gathering information from diverse Internet repositories and their subsequent effective use. The architecture enables the construction of topic specific content indexes (broker) but the definition of a personalized view is not supported directly. As ....

Darren R. Hardy, Michael F. Schwartz, and Duane Wessels. Harvest User's Manual. University of Colorado, January 1996. Version 1.4 patchlevel 2. !URL: http://harvest.transarc.com/afs/transarc.com/public/trg/Harvest/user-manual.ps?

....One level of aggregation beyond the individual attribute is the attribute model a self contained collection of attributes. Well known attribute models include the USMARC set of bibliographic attributes (referred to as fields in the USMARC community) 22] the Dublin Core set of attributes [24], and so on. In our metadata architecture, we reify both attributes and their encompassing attribute models as first class objects. Attributes are instances of class AttributeItem. Attribute model proxies are implemented as InfoBus collections. Attribute model proxies represent real world ....

....hence our decision to make them retrievable using ftp, for example, instead of using our protocol. The content summary follows the STARTS content summaries, and consists of the information that a resource discovery service like GlOSS [7] needs. Content summaries are formatted as Harvest SOIFs [24]. The second metadata object returned by the getMetadata( method contains attribute access characteristics. This is attribute specific information for each attribute that the proxy supports. Recall that attribute model proxies contain only information that is independent from any particular ....

Hardy D.R., M.F. Schwartz, and D. Wessels (1996). Harvest User's Manual. Accessible at http:// harvest.transarc.com/-afs/-transarc.com/-public/-trg/-Harvest/-user-manual/.

....One level of aggregation beyond the individual attribute is the attribute model a self contained collection of attributes. Well known attribute models include the USMARC set of bibliographic attributes (referred to as fields in the USMARC community) 22] the Dublin Core set of attributes [24], and so on. In our metadata architecture, we reify both attributes and their encompassing attribute models as first class objects. Attributes are instances of class AttributeItem. Attribute model proxies are implemented as InfoBus collections. Attribute model proxies represent real world ....

....hence our decision to make them retrievable using ftp, for example, instead of using our protocol. The content summary follows the STARTS content summaries, and consists of the information that a resource discovery service like GlOSS [7] needs. Content summaries are formatted as Harvest SOIFs [24]. The second metadata object returned by the getMetadata( method contains attribute access characteristics. This is attribute specific information for each attribute that the proxy supports. Recall that attribute model proxies contain only information that is independent from any particular ....

Hardy D.R., M.F. Schwartz, and D. Wessels (1996). Harvest User's Manual. Accessible at http:// harvest.transarc.com/-afs/-transarc.com/-public/-trg/-Harvest/-user-manual/.

....two extremes meta search engines (MetaCrawler [25] SavvySearch 16 ) and networked literature collections (NCSTRL 17 ) overcome the latter interface diversity, but problems remain: predefined search space not configurable by the user, restricted retrieval capabilities. The Harvest system (see [6, 16]) is an integrated set of customizable tools for gathering information from diverse Internet repositories and their subsequent effective use. The architecture enables the construction of topic specific content indexes, but the definition of a personalized view is not supported directly. ....

Darren R. Hardy, Michael F. Schwartz, and Duane Wessels. Harvest User's Manual. University of Colorado, January 1996. Version 1.4 patchlevel 2. !URL: http://harvest.transarc.com/afs/transarc.com/public/trg/Harvest/user-manual.ps?

....documents until the given depth is reached and builds the thesaurus according to the process described in section 1. The results are directly sent to the view managers (clients) and stored in a database. The way the index server works is comparable to other information servers such as Harvest [14]. The main difference is that our server builds thesauri from the analysis of the documents retrieved rather than regular indexes. Although we chose to build a server for this particular purpose, adding an extension to a more general purpose server would be possible. The view manager builds ....

Hardy, Schwartz, and Wessels. Harvest user's manual. University of Colorado.

....Replicator in the Internet. The HSR is useful when searching for an appropriate Broker, and when constructing new Gatherers and Brokers, to avoid duplication of effort. Gatherers and Brokers communicate using an attribute value stream protocol called the Summary Object Interchange Format (SOIF) [27], intended to be easily parsed yet sufficiently expressive to handle many kinds of objects. It delineates streams of object summaries, and allows for multiple levels of nested detail. SOIF is based on a combination of the Internet Anonymous FTP Archives (IAFA) IETF Working Group templates [19] and ....

Darren R. Hardy and Michael F. Schwartz. Harvest user's manual. Technical report, February 1995. Version 1.1.

No context found.

Hardy D.R., M.F. Schwartz, and D. Wessels (1996). Harvest User's Manual. Accessible at http:// harvest.transarc.com/-afs/-transarc.com/-public/-trg/-Harvest/-user-manual/.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC