<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-09-19T09:49:41Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/42128" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/42128</identifier><datestamp>2022-01-13T07:54:29Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131023</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="advisor" lang="en_US">John R. Williams and Abel Sanchez.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Yu, Indy (Indy Yin)</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Dept. of Electrical Engineering and Computer Science.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Department of Electrical Engineering and Computer Science</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2008-09-03T14:40:16Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2008-09-03T14:40:16Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2007</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2007</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/42128</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">227813909</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (M. Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2007.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 69-70).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">As the use of RFID technology penetrates and reforms the supply-chain industry, standards are being produced at all levels of the RFID technology spectrum, ranging from hardware to software. The Electronic Product Code (EPC) standard uniquely identifies RFID-tagged products. An application that supports the usage of EPCs is an Electronic Drug Pedigree (E-Pedigree), which is a historical record that indicates the chain of custody of a particular drug product being passed from one supply-chain partner to another. In order to fully implement track-and-trace of pharmaceutical products, software systems need to be built so that pedigree documents can be effectively stored and searched. In this Thesis, two approaches that address the issue of pedigree document discovery are presented-one centralized, one decentralized. The centralized pedigree discovery service extracts metadata from pedigree documents submitted to a centralized server and uses them in a search engine, such as Google Base, to located desired documents that match client queries. The decentralized service allows pedigree documents to be stored locally by individual business owners. Each local server is attached to a Discovery Service Unit containing metadata of local pedigree documents, and these units communicate with each other to form a network. Both approaches are implemented as Web Services.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Indy Yu.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">M.Eng.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">70 p.</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en_US">eng</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en_US">Massachusetts Institute of Technology</dim:field>
   <dim:field mdschema="dc" element="rights" lang="en_US">M.I.T. theses are protected by 
copyright. They may be viewed from this source for any purpose, but 
reproduction or distribution in any format is prohibited without written 
permission. See provided URL for inquiries about permission.</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri" lang="en_US">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Electrical Engineering and Computer Science.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">A comparative approach to the implementation of drug pedigree discovery systems</dim:field>
   <dim:field mdschema="dc" element="type" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dspace" element="authorsordered">false</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="cerif" element="openaire" authority="" confidence="-1">&lt;Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="d6ea0661-7ed8-4b66-83a2-2a590cb5ac1f">
	&lt;Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843&lt;/Type>
	&lt;Language>eng&lt;/Language>
   	&lt;Title>A comparative approach to the implementation of drug pedigree discovery systems&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2007&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Yu, Indy (Indy Yin)&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
	&lt;/Authors>
   	&lt;Editors>
	&lt;/Editors>
    &lt;Publishers>
        &lt;Publisher>
            &lt;DisplayName>Massachusetts Institute of Technology&lt;/DisplayName>
            &lt;OrgUnit />
        &lt;/Publisher>
    &lt;/Publishers>
    &lt;License>http://dspace.mit.edu/handle/1721.1/7582&lt;/License>
    &lt;Keyword>Electrical Engineering and Computer Science.&lt;/Keyword>
   	&lt;Abstract>As the use of RFID technology penetrates and reforms the supply-chain industry, standards are being produced at all levels of the RFID technology spectrum, ranging from hardware to software. The Electronic Product Code (EPC) standard uniquely identifies RFID-tagged products. An application that supports the usage of EPCs is an Electronic Drug Pedigree (E-Pedigree), which is a historical record that indicates the chain of custody of a particular drug product being passed from one supply-chain partner to another. In order to fully implement track-and-trace of pharmaceutical products, software systems need to be built so that pedigree documents can be effectively stored and searched. In this Thesis, two approaches that address the issue of pedigree document discovery are presented-one centralized, one decentralized. The centralized pedigree discovery service extracts metadata from pedigree documents submitted to a centralized server and uses them in a search engine, such as Google Base, to located desired documents that match client queries. The decentralized service allows pedigree documents to be stored locally by individual business owners. Each local server is attached to a Discovery Service Unit containing metadata of local pedigree documents, and these units communicate with each other to form a network. Both approaches are implemented as Web Services.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>