1 |
dpavlin |
1 |
<table width="80%"> |
2 |
|
|
<tr> |
3 |
|
|
<td width="5"> |
4 |
|
|
|
5 |
|
|
</td> |
6 |
|
|
<td> |
7 |
|
|
<h3>What is a Master Information Type? What is a Master Subject?</h3> |
8 |
|
|
|
9 |
|
|
In the library world there are many, many different types of information. From encyclopedias |
10 |
|
|
to maps, field guides to catalogs, the list is seemingly endless. The authors of LibData carefully |
11 |
|
|
considered this reality when designing the system, hoping that they could categorize all these |
12 |
|
|
different information types, allow for the easy addition of new information types, and allow for |
13 |
|
|
the easy selection of information types when adding new resources. |
14 |
|
|
<br><br> |
15 |
|
|
|
16 |
|
|
The "Master Information Type" is the result of this effort. Let's say, for example, that you want |
17 |
|
|
to add a new article index to the database. Rather than wade through 50 or more information types |
18 |
|
|
before you came upon the correct one for your index, you could select "Periodical Indexes" at the |
19 |
|
|
beginning and have the system limit your potential information types to only those that have to do |
20 |
|
|
with Periodical Indexes. The other "Master Information Types" work the same way and allow the user |
21 |
|
|
to limit the potential number of pertinent information types for his/her new resource. |
22 |
|
|
<br><br> |
23 |
|
|
|
24 |
|
|
The second problem the authors of LibData tried to alleviate is the problem of subject specific |
25 |
|
|
information types. One example is Spectra. Spectra, and all its varieties, is an important |
26 |
|
|
information type for science and engineering, but obviously not important in the humanities. Why |
27 |
|
|
should users entering resources for the humanities have to see this information type? And why |
28 |
|
|
should those in science and engineering have to see humanities specific information types? |
29 |
|
|
<br><br> |
30 |
|
|
|
31 |
|
|
The "Master Subject" is our attempt at alleviating this problem. The "Master Subject" designation |
32 |
|
|
allows us to add very subject specific information types without cluttering up the system for users |
33 |
|
|
that will never need those information types. Now, when a user knows he or she is adding a Spectra |
34 |
|
|
resource, he or she will first select "Science and Engineering" from the "Master Subject" list to |
35 |
|
|
be shown those information types, as well as all the standard information types. The |
36 |
|
|
"Master Subject" concept will also allow us to add many new information types that we may have |
37 |
|
|
rejected since we can keep subject specific information types sequestered from those users that |
38 |
|
|
will never use them. |
39 |
|
|
|
40 |
|
|
|
41 |
|
|
</td> |
42 |
|
|
</tr> |
43 |
|
|
</table> |