UDC implementation: from library shelves to a structured indexing language
dc.contributor.author | Slavic, Aida | |
dc.date.accessioned | 2005-01-10T00:00:01Z | |
dc.date.available | 2010-06-18T23:31:51Z | |
dc.date.issued | 2004 | en_US |
dc.date.submitted | 2005-01-10 | en_US |
dc.identifier.citation | UDC implementation: from library shelves to a structured indexing language 2004, 33(3):60-65 International Cataloguing and Bibliographic Control | en_US |
dc.identifier.uri | http://hdl.handle.net/10150/105685 | |
dc.description.abstract | The UDC is attractive to different stakeholders across the information sector because of its wide-spread application, large vocabulary and availability in an electronic format. Modern information retrieval systems have the need but also the capacity to support flexible and interactive retrieval systems. The role of classification in such systems is to serve as an underlying knowledge structure that provides systematic subject organisation and thus complements the search using natural language terms. There are, however, specific requirements that must be satisfied in order to make efficient use of classification and these are not well known outside the library domain and are poorly implemented in library systems. This is especially the case for synthetic classifications, such as UDC, because its elements are meant to be manipulated by the system to fulfill different functions (a flexible systematic display, browsing or search purposes). This report summarizes the most important functionalities of the UDC that need to be taken into account during the implementation process. Important issues about the relation between the UDC schedules in electronic form - UDC Master Reference File and a classification tool (an authority file) that may be built on it, are highlighted. A better understanding of the UDC system's functionality may improve or facilitate its implementation and lower the costs of system maintenance which may be relevant for both prospective users and legacy systems. | |
dc.format.mimetype | doc | en_US |
dc.language.iso | en | en_US |
dc.publisher | IFLA | en_US |
dc.subject | Classification | en_US |
dc.subject.other | Universal Decimal Classification | en_US |
dc.subject.other | Implementation | en_US |
dc.subject.other | Information retrieval | en_US |
dc.subject.other | Management | en_US |
dc.subject.other | Authority file | en_US |
dc.title | UDC implementation: from library shelves to a structured indexing language | en_US |
dc.type | Journal Article (Paginated) | en_US |
dc.identifier.journal | International Cataloguing and Bibliographic Control | en_US |
html.description.abstract | The UDC is attractive to different stakeholders across the information sector because of its wide-spread application, large vocabulary and availability in an electronic format. Modern information retrieval systems have the need but also the capacity to support flexible and interactive retrieval systems. The role of classification in such systems is to serve as an underlying knowledge structure that provides systematic subject organisation and thus complements the search using natural language terms. There are, however, specific requirements that must be satisfied in order to make efficient use of classification and these are not well known outside the library domain and are poorly implemented in library systems. This is especially the case for synthetic classifications, such as UDC, because its elements are meant to be manipulated by the system to fulfill different functions (a flexible systematic display, browsing or search purposes). This report summarizes the most important functionalities of the UDC that need to be taken into account during the implementation process. Important issues about the relation between the UDC schedules in electronic form - UDC Master Reference File and a classification tool (an authority file) that may be built on it, are highlighted. A better understanding of the UDC system's functionality may improve or facilitate its implementation and lower the costs of system maintenance which may be relevant for both prospective users and legacy systems. |