The structure of a knowledge base for cataloging rules
Identifieur interne : 001885 ( Istex/Corpus ); précédent : 001884; suivant : 001886The structure of a knowledge base for cataloging rules
Auteurs : Ling Hwey JengSource :
- Information Processing and Management [ 0306-4573 ] ; 1990.
Abstract
This article reports on a pilot study that investigates the general patterns and the level of applicability of rules in the AACR2. It studies those rules in the AACR2 related to the title and statement of responsibility area. It attempts to answer two research questions: (1) What is a rule in the AACR2? (2) What are the application domains for the rules? Rule numbers in the AACR2 are divided into two kinds: the rule numbers followed by text and those followed by a set of subrules. Prototype expert systems designed for cataloging as reported in literature have used the former as the defining unit in their knowledge base. However, the study finds that a rule number with text usually consists of many pairs of condition and action (C/A); each pair is a subrule. The analysis of actual application of rules further suggests that the level of applicability of a rule is usually limited. Rules are designed for five major application domains: definition, description, organization, source of information identification, and transcription. Findings of this study suggest that a knowledge base for cataloging rules must base its defining unit on the C/A pair and not the rule number. The structure of each C/A pair in the knowledge base must contain the application domain, the procedural interpretation, the level of applicability, and the condition and action as stated in the text.
Url:
DOI: 10.1016/0306-4573(91)90033-I
Links to Exploration step
ISTEX:2173DE9D69545AA1A93EFE54BC1C5BBA886320ADLe document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title>The structure of a knowledge base for cataloging rules</title><author><name sortKey="Jeng, Ling Hwey" sort="Jeng, Ling Hwey" uniqKey="Jeng L" first="Ling Hwey" last="Jeng">Ling Hwey Jeng</name><affiliation><mods:affiliation>College of Library and Information Services, University of Maryland, College Park, Maryland 20742-4345 U.S.A.</mods:affiliation></affiliation></author></titleStmt><publicationStmt><idno type="wicri:source">ISTEX</idno><idno type="RBID">ISTEX:2173DE9D69545AA1A93EFE54BC1C5BBA886320AD</idno><date when="1991" year="1991">1991</date><idno type="doi">10.1016/0306-4573(91)90033-I</idno><idno type="url">https://api.istex.fr/document/2173DE9D69545AA1A93EFE54BC1C5BBA886320AD/fulltext/pdf</idno><idno type="wicri:Area/Istex/Corpus">001885</idno></publicationStmt><sourceDesc><biblStruct><analytic><title level="a">The structure of a knowledge base for cataloging rules</title><author><name sortKey="Jeng, Ling Hwey" sort="Jeng, Ling Hwey" uniqKey="Jeng L" first="Ling Hwey" last="Jeng">Ling Hwey Jeng</name><affiliation><mods:affiliation>College of Library and Information Services, University of Maryland, College Park, Maryland 20742-4345 U.S.A.</mods:affiliation></affiliation></author></analytic><monogr></monogr><series><title level="j">Information Processing and Management</title><title level="j" type="abbrev">IPM</title><idno type="ISSN">0306-4573</idno><imprint><publisher>ELSEVIER</publisher><date type="published" when="1990">1990</date><biblScope unit="volume">27</biblScope><biblScope unit="issue">1</biblScope><biblScope unit="page" from="97">97</biblScope><biblScope unit="page" to="110">110</biblScope></imprint><idno type="ISSN">0306-4573</idno></series><idno type="istex">2173DE9D69545AA1A93EFE54BC1C5BBA886320AD</idno><idno type="DOI">10.1016/0306-4573(91)90033-I</idno><idno type="PII">0306-4573(91)90033-I</idno></biblStruct></sourceDesc><seriesStmt><idno type="ISSN">0306-4573</idno></seriesStmt></fileDesc><profileDesc><textClass></textClass><langUsage><language ident="en">en</language></langUsage></profileDesc></teiHeader><front><div type="abstract" xml:lang="en">This article reports on a pilot study that investigates the general patterns and the level of applicability of rules in the AACR2. It studies those rules in the AACR2 related to the title and statement of responsibility area. It attempts to answer two research questions: (1) What is a rule in the AACR2? (2) What are the application domains for the rules? Rule numbers in the AACR2 are divided into two kinds: the rule numbers followed by text and those followed by a set of subrules. Prototype expert systems designed for cataloging as reported in literature have used the former as the defining unit in their knowledge base. However, the study finds that a rule number with text usually consists of many pairs of condition and action (C/A); each pair is a subrule. The analysis of actual application of rules further suggests that the level of applicability of a rule is usually limited. Rules are designed for five major application domains: definition, description, organization, source of information identification, and transcription. Findings of this study suggest that a knowledge base for cataloging rules must base its defining unit on the C/A pair and not the rule number. The structure of each C/A pair in the knowledge base must contain the application domain, the procedural interpretation, the level of applicability, and the condition and action as stated in the text.</div></front></TEI><istex><corpusName>elsevier</corpusName><author><json:item><name>Ling Hwey Jeng</name><affiliations><json:string>College of Library and Information Services, University of Maryland, College Park, Maryland 20742-4345 U.S.A.</json:string></affiliations></json:item></author><language><json:string>eng</json:string></language><abstract>This article reports on a pilot study that investigates the general patterns and the level of applicability of rules in the AACR2. It studies those rules in the AACR2 related to the title and statement of responsibility area. It attempts to answer two research questions: (1) What is a rule in the AACR2? (2) What are the application domains for the rules? Rule numbers in the AACR2 are divided into two kinds: the rule numbers followed by text and those followed by a set of subrules. Prototype expert systems designed for cataloging as reported in literature have used the former as the defining unit in their knowledge base. However, the study finds that a rule number with text usually consists of many pairs of condition and action (C/A); each pair is a subrule. The analysis of actual application of rules further suggests that the level of applicability of a rule is usually limited. Rules are designed for five major application domains: definition, description, organization, source of information identification, and transcription. Findings of this study suggest that a knowledge base for cataloging rules must base its defining unit on the C/A pair and not the rule number. The structure of each C/A pair in the knowledge base must contain the application domain, the procedural interpretation, the level of applicability, and the condition and action as stated in the text.</abstract><qualityIndicators><score>7.736</score><pdfVersion>1.2</pdfVersion><pdfPageSize>504 x 756 pts</pdfPageSize><refBibsNative>true</refBibsNative><keywordCount>0</keywordCount><abstractCharCount>1385</abstractCharCount><pdfWordCount>6966</pdfWordCount><pdfCharCount>41198</pdfCharCount><pdfPageCount>14</pdfPageCount><abstractWordCount>228</abstractWordCount></qualityIndicators><title>The structure of a knowledge base for cataloging rules</title><pii><json:string>0306-4573(91)90033-I</json:string></pii><genre><json:string>research-article</json:string></genre><serie><volume>vol. 25</volume><pages><last>35</last><first>31</first></pages><genre></genre><language><json:string>unknown</json:string></language><title>ASIS '88: The proceedings of the 51st ASIS annual meeting. Atlanta, Georgia</title></serie><host><volume>27</volume><pii><json:string>S0306-4573(00)X0051-9</json:string></pii><pages><last>110</last><first>97</first></pages><issn><json:string>0306-4573</json:string></issn><issue>1</issue><genre><json:string>Journal</json:string></genre><language><json:string>unknown</json:string></language><title>Information Processing and Management</title><publicationDate>1991</publicationDate></host><categories><wos><json:string>COMPUTER SCIENCE, INFORMATION SYSTEMS</json:string><json:string>INFORMATION SCIENCE & LIBRARY SCIENCE</json:string></wos></categories><publicationDate>1990</publicationDate><copyrightDate>1991</copyrightDate><doi><json:string>10.1016/0306-4573(91)90033-I</json:string></doi><id>2173DE9D69545AA1A93EFE54BC1C5BBA886320AD</id><fulltext><json:item><original>true</original><mimetype>application/pdf</mimetype><extension>pdf</extension><uri>https://api.istex.fr/document/2173DE9D69545AA1A93EFE54BC1C5BBA886320AD/fulltext/pdf</uri></json:item><json:item><original>true</original><mimetype>text/plain</mimetype><extension>txt</extension><uri>https://api.istex.fr/document/2173DE9D69545AA1A93EFE54BC1C5BBA886320AD/fulltext/txt</uri></json:item><json:item><original>false</original><mimetype>application/zip</mimetype><extension>zip</extension><uri>https://api.istex.fr/document/2173DE9D69545AA1A93EFE54BC1C5BBA886320AD/fulltext/zip</uri></json:item><istex:fulltextTEI uri="https://api.istex.fr/document/2173DE9D69545AA1A93EFE54BC1C5BBA886320AD/fulltext/tei"><teiHeader><fileDesc><titleStmt><title level="a">The structure of a knowledge base for cataloging rules</title></titleStmt><publicationStmt><authority>ISTEX</authority><publisher>ELSEVIER</publisher><availability><p>ELSEVIER</p></availability><date>1991</date></publicationStmt><notesStmt><note>Based on projects funded by the OCLC Library and Information Science Research Program and the Council on Library Resources, CLR #4050.</note></notesStmt><sourceDesc><biblStruct type="inbook"><analytic><title level="a">The structure of a knowledge base for cataloging rules</title><author><persName><forename type="first">Ling Hwey</forename><surname>Jeng</surname></persName><affiliation>College of Library and Information Services, University of Maryland, College Park, Maryland 20742-4345 U.S.A.</affiliation></author></analytic><monogr><title level="j">Information Processing and Management</title><title level="j" type="abbrev">IPM</title><idno type="pISSN">0306-4573</idno><idno type="PII">S0306-4573(00)X0051-9</idno><imprint><publisher>ELSEVIER</publisher><date type="published" when="1990"></date><biblScope unit="volume">27</biblScope><biblScope unit="issue">1</biblScope><biblScope unit="page" from="97">97</biblScope><biblScope unit="page" to="110">110</biblScope></imprint></monogr><idno type="istex">2173DE9D69545AA1A93EFE54BC1C5BBA886320AD</idno><idno type="DOI">10.1016/0306-4573(91)90033-I</idno><idno type="PII">0306-4573(91)90033-I</idno></biblStruct></sourceDesc></fileDesc><profileDesc><creation><date>1991</date></creation><langUsage><language ident="en">en</language></langUsage><abstract xml:lang="en"><p>This article reports on a pilot study that investigates the general patterns and the level of applicability of rules in the AACR2. It studies those rules in the AACR2 related to the title and statement of responsibility area. It attempts to answer two research questions: (1) What is a rule in the AACR2? (2) What are the application domains for the rules? Rule numbers in the AACR2 are divided into two kinds: the rule numbers followed by text and those followed by a set of subrules. Prototype expert systems designed for cataloging as reported in literature have used the former as the defining unit in their knowledge base. However, the study finds that a rule number with text usually consists of many pairs of condition and action (C/A); each pair is a subrule. The analysis of actual application of rules further suggests that the level of applicability of a rule is usually limited. Rules are designed for five major application domains: definition, description, organization, source of information identification, and transcription. Findings of this study suggest that a knowledge base for cataloging rules must base its defining unit on the C/A pair and not the rule number. The structure of each C/A pair in the knowledge base must contain the application domain, the procedural interpretation, the level of applicability, and the condition and action as stated in the text.</p></abstract></profileDesc><revisionDesc><change when="1990-07-18">Registration</change><change when="1990">Published</change></revisionDesc></teiHeader></istex:fulltextTEI></fulltext><metadata><istex:metadataXml wicri:clean="Elsevier, elements deleted: tail"><istex:xmlDeclaration>version="1.0" encoding="utf-8"</istex:xmlDeclaration><istex:docType PUBLIC="-//ES//DTD journal article DTD version 4.5.2//EN//XML" URI="art452.dtd" name="istex:docType"></istex:docType><istex:document><converted-article version="4.5.2" docsubtype="fla"><item-info><jid>IPM</jid><aid>9190033I</aid><ce:pii>0306-4573(91)90033-I</ce:pii><ce:doi>10.1016/0306-4573(91)90033-I</ce:doi><ce:copyright type="unknown" year="1991"></ce:copyright></item-info><head><ce:article-footnote><ce:label>☆</ce:label><ce:note-para>Based on projects funded by the OCLC Library and Information Science Research Program and the Council on Library Resources, CLR #4050.</ce:note-para></ce:article-footnote><ce:title>The structure of a knowledge base for cataloging rules</ce:title><ce:author-group><ce:author><ce:given-name>Ling Hwey</ce:given-name><ce:surname>Jeng</ce:surname></ce:author><ce:affiliation><ce:textfn>College of Library and Information Services, University of Maryland, College Park, Maryland 20742-4345 U.S.A.</ce:textfn></ce:affiliation></ce:author-group><ce:date-received day="29" month="3" year="1990"></ce:date-received><ce:date-accepted day="18" month="7" year="1990"></ce:date-accepted><ce:abstract><ce:section-title>Abstract</ce:section-title><ce:abstract-sec><ce:simple-para>This article reports on a pilot study that investigates the general patterns and the level of applicability of rules in the AACR2. It studies those rules in the AACR2 related to the title and statement of responsibility area. It attempts to answer two research questions: (1) What is a rule in the AACR2? (2) What are the application domains for the rules? Rule numbers in the AACR2 are divided into two kinds: the rule numbers followed by text and those followed by a set of subrules. Prototype expert systems designed for cataloging as reported in literature have used the former as the defining unit in their knowledge base. However, the study finds that a rule number with text usually consists of many pairs of condition and action (C/A); each pair is a subrule. The analysis of actual application of rules further suggests that the level of applicability of a rule is usually limited. Rules are designed for five major application domains: definition, description, organization, source of information identification, and transcription. Findings of this study suggest that a knowledge base for cataloging rules must base its defining unit on the C/A pair and not the rule number. The structure of each C/A pair in the knowledge base must contain the application domain, the procedural interpretation, the level of applicability, and the condition and action as stated in the text.</ce:simple-para></ce:abstract-sec></ce:abstract></head></converted-article></istex:document></istex:metadataXml><mods version="3.6"><titleInfo><title>The structure of a knowledge base for cataloging rules</title></titleInfo><titleInfo type="alternative" contentType="CDATA"><title>The structure of a knowledge base for cataloging rules</title></titleInfo><name type="personal"><namePart type="given">Ling Hwey</namePart><namePart type="family">Jeng</namePart><affiliation>College of Library and Information Services, University of Maryland, College Park, Maryland 20742-4345 U.S.A.</affiliation><role><roleTerm type="text">author</roleTerm></role></name><typeOfResource>text</typeOfResource><genre type="research-article" displayLabel="Full-length article"></genre><originInfo><publisher>ELSEVIER</publisher><dateIssued encoding="w3cdtf">1990</dateIssued><dateValid encoding="w3cdtf">1990-07-18</dateValid><copyrightDate encoding="w3cdtf">1991</copyrightDate></originInfo><language><languageTerm type="code" authority="iso639-2b">eng</languageTerm><languageTerm type="code" authority="rfc3066">en</languageTerm></language><physicalDescription><internetMediaType>text/html</internetMediaType></physicalDescription><abstract lang="en">This article reports on a pilot study that investigates the general patterns and the level of applicability of rules in the AACR2. It studies those rules in the AACR2 related to the title and statement of responsibility area. It attempts to answer two research questions: (1) What is a rule in the AACR2? (2) What are the application domains for the rules? Rule numbers in the AACR2 are divided into two kinds: the rule numbers followed by text and those followed by a set of subrules. Prototype expert systems designed for cataloging as reported in literature have used the former as the defining unit in their knowledge base. However, the study finds that a rule number with text usually consists of many pairs of condition and action (C/A); each pair is a subrule. The analysis of actual application of rules further suggests that the level of applicability of a rule is usually limited. Rules are designed for five major application domains: definition, description, organization, source of information identification, and transcription. Findings of this study suggest that a knowledge base for cataloging rules must base its defining unit on the C/A pair and not the rule number. The structure of each C/A pair in the knowledge base must contain the application domain, the procedural interpretation, the level of applicability, and the condition and action as stated in the text.</abstract><note>Based on projects funded by the OCLC Library and Information Science Research Program and the Council on Library Resources, CLR #4050.</note><relatedItem type="host"><titleInfo><title>Information Processing and Management</title></titleInfo><titleInfo type="abbreviated"><title>IPM</title></titleInfo><genre type="Journal">journal</genre><originInfo><dateIssued encoding="w3cdtf">1991</dateIssued></originInfo><identifier type="ISSN">0306-4573</identifier><identifier type="PII">S0306-4573(00)X0051-9</identifier><part><date>1991</date><detail type="volume"><number>27</number><caption>vol.</caption></detail><detail type="issue"><number>1</number><caption>no.</caption></detail><extent unit="issue pages"><start>1</start><end>144</end></extent><extent unit="pages"><start>97</start><end>110</end></extent></part></relatedItem><identifier type="istex">2173DE9D69545AA1A93EFE54BC1C5BBA886320AD</identifier><identifier type="DOI">10.1016/0306-4573(91)90033-I</identifier><identifier type="PII">0306-4573(91)90033-I</identifier><recordInfo><recordContentSource>ELSEVIER</recordContentSource></recordInfo></mods></metadata><enrichments><istex:catWosTEI uri="https://api.istex.fr/document/2173DE9D69545AA1A93EFE54BC1C5BBA886320AD/enrichments/catWos"><teiHeader><profileDesc><textClass><classCode scheme="WOS">COMPUTER SCIENCE, INFORMATION SYSTEMS</classCode><classCode scheme="WOS">INFORMATION SCIENCE & LIBRARY SCIENCE</classCode></textClass></profileDesc></teiHeader></istex:catWosTEI></enrichments></istex></record>Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/OcrV1/Data/Istex/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 001885 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Istex/Corpus/biblio.hfd -nk 001885 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien
|wiki= Ticri/CIDE
|area= OcrV1
|flux= Istex
|étape= Corpus
|type= RBID
|clé= ISTEX:2173DE9D69545AA1A93EFE54BC1C5BBA886320AD
|texte= The structure of a knowledge base for cataloging rules
}}
| This area was generated with Dilib version V0.6.32. |  |