Costruzione di thesauri » Cronologia » Versione 11
Redmine Admin, 23-01-2020 17:16
1 | 1 | Redmine Admin | h1. Costruzione di thesauri |
---|---|---|---|
2 | |||
3 | h2. Definizione di thesaurus |
||
4 | |||
5 | 2 | Redmine Admin | _A tool for vocabulary control of a specific subject domain_ (1) |
6 | 1 | Redmine Admin | |
7 | 2 | Redmine Admin | _It contains_: |
8 | * _Preferred terms and non-preferred terms_ |
||
9 | * _The semantic relations between terms_ |
||
10 | * _Rules for use and other administrative information_ |
||
11 | 3 | Redmine Admin | |
12 | 2 | Redmine Admin | _It presupposes_: |
13 | 8 | Redmine Admin | * _*A particular collection of documents*_ |
14 | * _*A particular group of users*_ |
||
15 | 1 | Redmine Admin | |
16 | 6 | Redmine Admin | According to Foskett (1980), the purposes of the thesaurus are |
17 | 10 | Redmine Admin | |
18 | * To provide a map of a given field of knowledge. |
||
19 | 9 | Redmine Admin | * *To provide a standard vocabulary for a given subject field*. |
20 | * To provide a system of references between terms. |
||
21 | * To provide a guide for users of the system. |
||
22 | * To locate new concepts in a scheme of relationships with existing concepts in a way which, makes sense to users of the system. |
||
23 | * To provide classified hierarchies. |
||
24 | * To provide means by which the use of terms in given subject field may be standardized. |
||
25 | 6 | Redmine Admin | |
26 | 1 | Redmine Admin | The thesaurus can also be used for generation of keyword lists which form the basis for planning, priority setting, and other research management tasks (Nestsel, et.al., 1992). The thesaurus is also useful in computer-assisted indexing and abstracting. Thesaurus helps in defining terms. |
27 | 6 | Redmine Admin | |
28 | Thesaurus can be used for three basic purposes (Rowley and Farrow, 2000a). |
||
29 | 8 | Redmine Admin | |
30 | # In indexing but not in searching. |
||
31 | # In searching but not in indexing. |
||
32 | # In both indexing and searching. |
||
33 | 7 | Redmine Admin | |
34 | 4 | Redmine Admin | h2. Strumenti per il controllo dei termini |
35 | |||
36 | 6 | Redmine Admin | |
37 | 4 | Redmine Admin | * List |
38 | * Synonym Ring |
||
39 | * Hierarchy |
||
40 | * Thesaurus |
||
41 | |||
42 | h3. List |
||
43 | |||
44 | Semplici elenchi di termini. |
||
45 | |||
46 | Applicazioni: inserimento dati (vocabolari di termini controllati per definire il dominio dei possibili valori delle unità di informazione) |
||
47 | |||
48 | h3. Synonym Ring |
||
49 | |||
50 | Elenchi di termini e relativi sinonimi. |
||
51 | |||
52 | Applicazioni: motori di ricerca (per aumentare la capacità di richiamo [recall] anche se a scapito della precisione) |
||
53 | |||
54 | h3. Hierarchy |
||
55 | |||
56 | Termini organizzati secondo una struttura ad albero (formalmente: grafo di nodi e archi indiretto aciclico e connesso) |
||
57 | |||
58 | Applicazioni: inserimento dati |
||
59 | |||
60 | Esempi: |
||
61 | |||
62 | * suddivisioni geografiche amministrative (regioni, province, comuni ISTAT) [https://www.istat.it/it/archivio/6789] |
||
63 | 1 | Redmine Admin | * schemi di classificazione iconografica (ICONCLASS [http://www.iconclass.org/help/outline] |
64 | 6 | Redmine Admin | * tassonomia linneana [https://upload.wikimedia.org/wikipedia/commons/b/bb/Linnaeus_-_Regnum_Animale_%281735%29.png] |
65 | 4 | Redmine Admin | |
66 | 6 | Redmine Admin | Relazioni di tipo isPartOf/hasPart, contains/isContained, derivedFrom, BT/NT tra classi o istanze |
67 | 4 | Redmine Admin | |
68 | 1 | Redmine Admin | h3. Thesaurus |
69 | 4 | Redmine Admin | |
70 | 6 | Redmine Admin | Esistono degli standard. |
71 | 5 | Redmine Admin | |
72 | Standard ISO 2788 (monolingua, 1974) [https://www.iso.org/standard/7776.html] |
||
73 | 1 | Redmine Admin | Standard ISO 5964 (multilingua, 1985) [https://www.iso.org/standard/12159.html] |
74 | 5 | Redmine Admin | Standard ISO 25964 (frutto del WG8 del NISO 2008-2013) [https://www.niso.org/schemas/iso25964] |
75 | Parte 1 e Parte 2 |
||
76 | 4 | Redmine Admin | Nella parte 2: Interoperabilità con SKOS: https://www.niso.org/schemas/iso25964#skos |
77 | 5 | Redmine Admin | Annuncio su W3: |
78 | 4 | Redmine Admin | Alignment between SKOS and new ISO 25964 thesaurus standard (2012-12-13) [https://www.w3.org/2004/02/skos/] |
79 | |||
80 | 1 | Redmine Admin | Modello UML: https://www.niso.org/schemas/iso25964/Model_2011-06-02.jpg |
81 | Schema XSD: https://www.niso.org/schemas/iso25964/iso25964-1_v1.4.xsd |
||
82 | |||
83 | 6 | Redmine Admin | Evoluzione di "termine" (e classiche relazioni BT,NT,UF) verso "concetto", più generico e dotato di maggiore potere espressivo formale. |
84 | |||
85 | SKOS Simple Knowledge Organization System Reference |
||
86 | https://www.w3.org/TR/skos-reference/ |
||
87 | |||
88 | https://www.w3.org/TR/skos-reference/#vocab |
||
89 | |||
90 | h4. Coordinamento (pre vs post) |
||
91 | |||
92 | Coordination refers to the construction of phrases from individual terms. Two distinct coordination options are recognized in thesauri: precoordination and post-coordination. A *precoordinated* thesaurus is one that *can contain phrases*. Consequently, phrases are available for indexing and retrieval. A *postcoordinated* thesaurus *does not allow phrases*. Instead, phrases are constructed while searching. The choice between the two options is difficult. The advantage in precoordination is that the vocabulary is very precise, thus reducing ambiguity in indexing and in searching. Also, commonly accepted phrases become part of the vocabulary. However, the disadvantage is that the searcher has to be aware of the phrase construction rules employed. Thesauri can adopt an intermediate level of coordination by allowing both phrases and single words. This is typical of manually constructed thesauri. However, even within this group there is significant variability in terms of coordination level. Some thesauri may emphasize two or three word phrases, while others may emphasize even larger sized phrases. Therefore, it is insufficient to state that two thesauri are similar simply because they follow precoordination. The level of coordination is important as well. It should be recognized that the higher the level of coordination, the greater the precision of the vocabulary but the larger the vocabulary size. It also implies an increase in the number of relationships to be encoded. Therefore, the thesaurus becomes more complex. The advantage in postcoordination is that the user need not worry about the exact ordering of the words in a phrase. Phrase combinations can be created as and when appropriate during searching. The disadvantage is that search precision may fall, as illustrated by the following well known example, from Salton and McGill (1983): the distinction between phrases such as "Venetian blind" and "blind Venetian" may be lost. A more likely example is "library school" and "school library." The problem is that unless search strategies are designed carefully, irrelevant items may also be retrieved. Precoordination is more common in manually constructed thesauri. Automatic phrase construction is still quite difficult and therefore automatic thesaurus construction usually implies post-coordination. Section 9.4 includes a procedure for automatic phrase construction. |
||
93 | |||
94 | |||
95 | 1 | Redmine Admin | Riferimenti: |
96 | Dextre Clarke, Stella G. and Zeng, Marcia Lei From ISO 2788 to ISO 25964: The evolution of thesaurus standards towards interoperability and data modelling. Information Standards Quarterly (ISQ), 2012, vol. 24, n. 1 |
||
97 | [http://eprints.rclis.org/16818/1/SP_clarke_zeng_isqv24no1.pdf] |
||
98 | 6 | Redmine Admin | |
99 | Kumbhar, Rajendra Madhavrao, Contruction of vocabulary control tool thesaurus for library and information science, Dr. Babasaheb Ambedkar Marathwada University, 2003 |
||
100 | [http://shodhganga.inflibnet.ac.in:8080/jspui/handle/10603/150911] |
||
101 | |||
102 | 11 | Redmine Admin | Introduzione all'indicizzazione / Serafina Spinelli |
103 | [http://web.dfc.unibo.it/buzzetti/IUcorso2008-09/mdidattici/spinelli-indicizzazione.htm] |
||
104 | |||
105 | Introduzione ai thesauri / S. Spinelli |
||
106 | [http://web.dfc.unibo.it/buzzetti/IUcorso2008-09/mdidattici/spinelli-thesauri.htm] |
||
107 | 4 | Redmine Admin | |
108 | |||
109 | 5 | Redmine Admin | Note |
110 | 1 | Redmine Admin | -------------- |
111 | (1) Rich Gazan, CONTROLLED VOCABULARY & THESAURUS DESIGN - Trainee’s Manual, p. 59 (session 5-7 |
||
112 | [https://www.loc.gov/catworkshop/courses/thesaurus/pdf/cont-vocab-thes-trnee-manual.pdf] |