slis 5200: iop template, spring 2008bkb0099.pbworks.com/f/iop-5200-final.doc  · web viewthey can...

44
Benjamin Baron Spring 2009 SLIS 5200 TXWI-C Final Draft 4 The North Texas Rock Music Appreciation Society: Information Organization System 1. Project description 1.1. Collection and information objects The North Texas Rock Music Appreciation Society collection consists of 1276 compact discs, housed in a converted Victorian style house in downtown Frisco, Texas. These musical works span a variety of Rock and Roll genres, from both American and European artists, and all objects in the collection were produced after 1960. Donations and Society purchases are the primary method by which the collection is developed. The Society exists for the purpose of educating young people in music appreciation and in exposing members to styles of music to which they are not otherwise exposed. This collection serves many of the suburban areas north of Dallas, Texas. 1.2. Users' demographics and knowledge Membership in the Society consists of 337 official members. Patrons of the collection are drawn from a variety of backgrounds, and represent all racial groups within the local community, with the majority of users coming from Caucasian and Asian backgrounds. The ages of members range from 16 to 37 years, representing a wide cross-section of experiences and socioeconomic backgrounds. Overall membership is represented by large groups of secondary school students and college students, with a much smaller percentage of postgraduate students existing within the group. A wide variety of life experiences are represented, especially when considered in terms of age and education. Domain knowledge represents collected knowledge on a subject or field of inquiry. Members of the Society are often self-educated in the field of rock music, exhibiting a moderate level of domain knowledge on the subject of rock and roll. In terms of the ability to use computer based search systems, members show a moderate level of system knowledge, as they are familiar with the use of computers and search software to find and access information.

Upload: others

Post on 19-Oct-2020

8 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Benjamin BaronSpring 2009

SLIS 5200 TXWI-CFinal Draft 4

The North Texas Rock Music Appreciation Society: Information Organization System

1. Project description

1.1. Collection and information objects

The North Texas Rock Music Appreciation Society collection consists of 1276 compact discs, housed in a converted Victorian style house in downtown Frisco, Texas. These musical works span a variety of Rock and Roll genres, from both American and European artists, and all objects in the collection were produced after 1960. Donations and Society purchases are the primary method by which the collection is developed.

The Society exists for the purpose of educating young people in music appreciation and in exposing members to styles of music to which they are not otherwise exposed. This collection serves many of the suburban areas north of Dallas, Texas.

1.2. Users' demographics and knowledge

Membership in the Society consists of 337 official members. Patrons of the collection are drawn from a variety of backgrounds, and represent all racial groups within the local community, with the majority of users coming from Caucasian and Asian backgrounds. The ages of members range from 16 to 37 years, representing a wide cross-section of experiences and socioeconomic backgrounds. Overall membership is represented by large groups of secondary school students and college students, with a much smaller percentage of postgraduate students existing within the group.

A wide variety of life experiences are represented, especially when considered in terms of age and education. Domain knowledge represents collected knowledge on a subject or field of inquiry. Members of the Society are often self-educated in the field of rock music, exhibiting a moderate level of domain knowledge on the subject of rock and roll. In terms of the ability to use computer based search systems, members show a moderate level of system knowledge, as they are familiar with the use of computers and search software to find and access information.

Finally, members display high information seeking behavior, as they often actively seek out new information connected to information they already possess. This group of users shows a high level of sophistication as evidenced by the sometimes complex and specific nature of their questions. This level of behavior results in users consulting a variety of resources regarding the subject in which they are interested, such as magazines, websites, video resources, and other text resources. Such behavior also results in the use of narrowly scoped initial information in order to seek out related materials of a much wider scope. Based on these user characteristics, an information system for this collection must be able to address moderately specific questions while presenting the user with a variety of search options.

1.3. Users' problems and questions

Member inquiries often address a variety of terms describing the material within the collection. Among the topics of these questions are artists or performers, producer information, copyright dates, and related

Page 2: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 2

sub-genres. All of these questions can be primarily addressed from the subject of musical sub genre, within the overall genre of rock and roll. Members of the society often seek to expand their musical horizons and knowledge by researching musical acts or recordings related to their current level of domain knowledge. Often this is accomplished by searching for information related to artists within a genre or by delving further into related genres. Members may also seek information regarding more esoteric aspects of a musical work, such as names of producers, nationalities of artists, or the presence of mutual members of a musical act.

Member questions exhibit wide variation in both the precision and desired recall of their searches. Precision refers to desired specificity of actual search results to a search query, and recall is a quantitative expression of how much information a user desires in order to address their question. Based on the users’ levels of knowledge as described, the following represent typical questions regarding the collection.

User question 1: “I am preparing a presentation on the Post-punk movement, and I need around seven to ten examples of musical works that developed out of this movement.”Object attributes: Genre.Desired precision: Low. The works are not asked for specifically, rather a range is necessary.Desired recall: High.

User question 2: “I enjoy Industrial music, especially the album “The Downward Spiral” by Nine Inch Nails. Can you show me 3 or 4 more titles involving the same band members or producers?”Object attributes: Genre, album, producer, artist, band members.Desired precision: High. Not only is it necessary to identify the members and producers of the album “The Downward Spiral”, but it is also necessary to then find titles involving those same individuals.Desired recall: Moderate.

User question 3: “I’d like one or two psychedelic albums performed by British musicians after the 1970’s.”Object attributes: Genre, nationality of artist, copyright date.Desired precision: High. Not only does the user specify the nationality of the artist, but albums released after a specific date are required.Desired recall: Low.

User question 4: “My parents don’t want me to listen to music with explicit lyrics. Can you show me some metal albums that I can listen to without getting in trouble?”Object attributes: Genre, content warning.Desired precision: Moderate. The user wants a variety of objects to choose from, but those objects must exhibit a specific characteristic.Desired recall: Moderate.

The user questions address a reasonable scope of attributes describing the materials within the collection. Based on the questions presented, it is necessary to include the attributes: genre, sub genre, album, producer, artist (including individuals and bands), nationality of artist, content warning, band members, copyright date.

Additionally, and for the purpose of including sufficient data for each object in the collection, a number of other attributes can apply to the objects in this collection, namely: song titles, label (publishing studio), special features (such as multiple discs, or SACD format), and UPC.

2. Representation of information objects

2.1. Entity level

Page 3: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 3

Entity level addresses the physical form and scope of any one object in a collection. The simplest example of an entity is a single piece of media such as a compact disc. Compact discs can be considered either as whole entities or as a collection of entities, or individual tracks of audio in this case. The manner in which a collection’s entity level is determined is based on the needs of the collection’s users.

Entity level is the initial basis upon which collections are organized and sets the method by which users may search a collection. This is an important distinction that must be made at the beginning of collection development, as decisions made at this step of the process affect the organization and usability of the overall collection. For example, it does not make sense to organize and classify a collection of music around recordings of two thousand individual audio tracks. While such a system presents very precise results to users, it is not practical for collection organization and causes significant changes to the search behavior required to browse the collection. A better choice in this case is to organize the collection around an entity level consisting of individual compact discs, which fulfills the users’ needs while creating a manageable organizational system.

For the purpose of this project, the entity level of the collection is based on single album titles of audio compact recordings; therefore, within the system, one database record represents one compact disc recording. Compact disc recordings that consist of multiple physical discs are considered as a single whole, based on the title of the album. This entity level is appropriate for the North Texas Rock Music Appreciation Society collection, as the entirety of the collection is built around the physical format of compact discs. This entity level is also appropriate for the users of the collection, as the majority of user search behavior is conducted based on a whole compact disc level.

2.2. Metadata elements and semantics

Metadata schemes organize and describe the attributes of an entity. Metadata elements within a metadata scheme represent the attributes of an entity as fields within a record. For example, a metadata scheme for a collection of audio recordings contains metadata elements including creator, title, publication date, genre, UPC, and classification, among many other potential metadata elements. The creation of a metadata scheme allows the database designer to organize a collection based on similar elements of individual metadata, eventually converting these elements into fields within a database file.

The North Texas Rock Music Appreciation Society’s collection is organized around nine metadata elements. A number of additional attributes are addressed in section 1.3, including song titles, label or publishing studio, special features, and UPC. For the purpose of this project, the attributes of song titles and record label have been eliminated as essential attributes for inclusion as metadata elements, as they do not address the user questions addressed in section 1.3.

Metadata addresses four specific user tasks: finding, identifying, selecting, and obtaining. In the task of finding a user applies known information, or conducts a search of the file, in order to find records that match the search criteria. For example, if a user knows the name of an artist, the user can then use that information as a search term to find related records. Elements that address the user task of finding are Creator, Title, and Subject, as these elements represent the most common attributes that a user knows about the object it is attempting to acquire. For example, a user searches for the Creator name “The Beatles”, and is presented with the names of several albums. The user has accomplished the task of finding by utilizing the Creator element.

Identifying is the process in which the user determines which record or records most appropriately correspond with the original goal of the search. For example, a user searches based on known information, such as Creator name, and then uses other information to identify which records are more closely related to the search criteria. In the metadata scheme for the North Texas Rock Music Appreciation Society’s collection, elements that address the user task of identifying are Creator, Title, Date, Subject, Feature, Nationality, Producer, and Identifier. All of these metadata elements relate to fields within the record that allow the user to identify specific features about a record that assist in

Page 4: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 4

identifying which records are appropriate to the search goals. Using the results from searching “The Beatles”, the user now identifies which album or albums meet the search criteria. In this case, the user is looking for the titles of albums produced before 1966. By utilizing the Date element, the user has identified a specific object or specific objects within the search results.

Selecting occurs after records are found, and after specific records are identified as appropriate to the search goals. Selecting is a process in which the user selects records from the file that most closely match the search criteria. At this point in the process the user may alter the criteria upon which they are searching based on selections related to the search results. As with identifying, a greater level of specificity is sought, typically by using the information contained in the returned records. Elements within the metadata scheme that address the user task of selecting are Creator, Title, Date, Feature, Nationality, Producer, and Identifier. The inclusion of these elements provides users with detailed information contained in the records, and assists in the user task of selecting by allowing users to discriminate between the records. Now that the user has found and identified results using “The Beatles” and production dates before 1966, the user selects the most appropriate record or records by utilizing further information. If the user is searching for a re-mastered recording of the album, a record that fulfills this desire is selected using the Feature element. Since the North Texas Rock Music Appreciation Society serves a user group of varying domain knowledge the inclusion of specific fields serves those users who require narrowly focused information. While the most basic elements such as Creator, Title and Subject serve all users, more knowledgeable users require the use of elements such as Date, Feature, Nationality, Producer, and Identifier to produce results appropriate to sophisticated search criteria.

Finally, the task of obtaining occurs when a user gains access to the object or acquires the classification information that indicates the physical location of the object within a collection. The Classification element directly addresses this user task by providing a location address to the user. In the example, the user finds, identifies, and selects a specific version of an album produced by the Beatles previous to 1966. Using the Classification information, the user can now physically acquire the results of the search.

Metadata elements within a metadata scheme can be described as container or content based. In the case of a container based element, such as Title, Date, and Identifier, information regarding the physical object is conveyed, while for a content based element, such a Subject or Classification, a relationship within the collection is described.

A complete list of the metadata elements and their related semantics are found in Appendix A, Metadata elements and semantics.

2.3. Record structure and specifications

In the creation of a database it is necessary to create fields that are connected to the metadata elements within the metadata structure. Metadata elements are sometimes represented on a one-for-one basis by the fields within a record, but in some cases it is necessary to split a single metadata element into multiple related fields. One instance of such a split is seen with the Creator element. Cases exist where multiple entities serve the role of creator for a musical work, such as composers, musicians, and arrangers. While all of these entities are creators, they each serve different roles in the creative process, and it may be appropriate to distinguish their individual roles within the database by defining specific fields, even though the fields all stem from the same initial metadata element.

There are fourteen fields present in the database for the North Texas Rock Music Appreciation Society’s collection. In the structure of the collection’s database there are two automatically generated fields: RecordID and RecordDate. RecordID refers to the unique database identifier for a record. This identifier is generated at the time of record entry. Therefore, the tenth record entered into the database is automatically assigned the RecordID of “10”. RecordDate refers to the actual date on which the record within the database was created. RecordID is indexed within the database, however RecordDate is not indexed. While neither field addresses the four user tasks in an efficient manner, RecordID has the potential to be of value to technical users, and so is automatically term indexed. Entry validation is

Page 5: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 5

automatically applied by the database software, and content validation is not appropriate as each entry is unique to the record as it is created.

In this project there are three instances of metadata elements that are split into multiple fields. First, the metadata element of Creator is split into the fields of Artist and Member. Artist refers to the individual artist or the musical act responsible for an original audio recording. Member refers to musicians who are members of a musical act. It may also refer to the individual artist referenced in the Artist field.

Second, the metadata element of Feature is split into the fields of Special Features and Content Warning. The Special Features field refers to qualitative features of a recording, such as Super Audio Compact Disc encoding, gold recording media, or a title that consists of multiple compact discs. The Content Warning field indicates the presence or lack of a content warning for an audio recording.

Finally, the metadata element of Subject is split into the fields of Genre and Sub Genre. Genre refers to top level terms which describe the music contained on each audio recording. Sub Genre refers to stylistic distinctions within a genre, and contains several levels of progressively specific yet related terms.

Field type addresses the technical format of a field. Common field types are text, number, and date. Within The North Texas Rock Music Appreciation Society’s database, five field types are utilized. The majority of the fields within the database utilize a text based field type, specifically the fields of Artist, Member, Title, Genre, Sub Genre, Special Features, Content Warning, Artist Nationality, and Producer. Entries in the Classification field utilize an assortment of alphanumeric characters; therefore the use of the text field type is appropriate for this field. The two exceptional fields within the database are the Date field, utilizing a date field type, and UPC, utilizing a number field type, as is appropriate to the respective content of these fields. Finally, RecordID utilizes the field type of autonumber while RecordDate utilizes the field type of autodate, both of which are specialized field types automatically generated by the database software.

In the most basic sense, indexing occurs when a record is created. This process is also referred to as cataloging. In a technical sense, indexing occurs when a field becomes searchable. For the purpose of this project the term “indexing” refers to this process. An indexed field may also be referred to as an access point. By creating a searchable field, or an access point, users are provided with access to the information contained in the individual records. In an inverted index the database software creates separate index files for each indexed field. So, in the case of the Artist field, a smaller index is created with all the artist names for the records in the database file. Pointers are created by the software to connect this smaller index to the appropriate records within the file. This is important because the design of the inverted index affects the search process of the database. Rather than simply cull through each record in sequential order, the database searches the indexes of the fields that have been searched, Artist and Date for example. The software searches the indexes for the search term given for Artist and the search term given for Date, and then compares the valid results for each field index. The combined results for the field index searches are then given to the user as the search results.

Fields can be indexed in a number of ways. They can be indexed by word, indexed by term, or indexed by both word and term. Fields that are not indexed are unsearchable. A word indexed field requires a single word entry for searches, and is appropriate for fields that serve users who tend to browse for information. The search results returned by term indexing is more precise because it relies on the use of specific terms for quality results, and is better suited to users with very specific search goals. Term indexed fields often involves controlled vocabularies due to the specificity. A blend of word and term indexing is possible, and is a more flexible way to allow users to search, however, such indexing often requires the use of Boolean search operators such as “and” and “or” in order to provide effective search results.

Within the North Texas Rock Music Appreciation Society’s database, there are six indexed fields. Term indexed fields are Sub Genre and Classification. The Sub Genre field contains data which is more specific than the Genre field and it serves users who exhibit the targeted search behavior. Term and word indexed fields are Artist, Member, Title, and Genre. Term and word indexed fields are specified due to

Page 6: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 6

the data contained within those fields, which may take the form of either single words or phrases. The flexibility of term and word indexing is appropriate to these fields, as these fields serve users that exhibit both targeted search behavior and general browsing behavior. All of the six indexed fields address the user task of finding by creating access points to the field indexes, allowing the user to access the information in the database. Thus, the indexing is of these fields is appropriate from a design viewpoint. RecordID is also term indexed as a default consequence of the software utilized for this project, but while it does not serve to address the user task of finding, it possesses the potential of utilization by technical users.

Entry validation is the process of setting limits upon data contained within a field. Entry validation does not specify how much data is contained within a field, only whether or not the data must meet a set of entry criteria. There are three methods to express how this process is accomplished. First, entry validation can be either required or not required. In a required setting, data must be entered into a field. This is an important form of entry validation because it denotes which fields are most significant to addressing search behavior. For example, when creating a record for an audio recording, the artist’s name and the title of the work must be entered into the record. Without this vital information, access points into the record do not exist and user searches for the record are fruitless. Likewise, requiring entry of the UPC for an audio recording serves the user by providing a field specific to the identity of the object. While the inclusion of the UPC does not directly address the current user tasks, it does serve as an additional unique identifying feature for the record. Requiring field entry for the color of a compact disc’s cover is not appropriate, as this information is not necessarily vital to the search behavior of the user.

Entry validation is required for all of the fields within the North Texas Rock Music Appreciation Society’s database, with the exception of the automatically generated fields of RecordID and RecordDate, and the Special Features field. Entry for the Special Features field is not required because not all objects in the database possess special features.

Single case entry validation is used to limit data entry for a field to one piece of data. This type of limit is used in cases where multiple entries are not appropriate for a field within a record. For example, an audio recording possesses only one UPC, therefore it is inappropriate to allow multiple entries in the UPC field of a record. Single case entry validation occurs in the RecordID, Title, Date, Content Warning, UPC, and Classification fields. All of these fields contain data that must have a single entry in order to avoid confusion associated with the entry of more than one piece of information per record. For example, an album does not have multiple titles and cannot both possess and lack a content warning.

Unique case entry validation is used to represent a unique piece of data contained within the file. This type of validation is applied to fields that express unique attributes of records that must not be replicated within the database. The Classification assigned to an audio recording is an example of unique case entry validation. Since each object in a collection must have a unique location identifier, the use of unique case entry validation is appropriate for the field of Classification within the North Texas Rock Music Appreciation Society’s database.

Depending on the circumstances associated with a field, combining the types of entry validation may be appropriate. As seen in the example of the Classification field, a situation exists where required entry, single entry, and unique entry validation are all appropriate for a single field within a record. Numerous permutations upon the types of entry validation are possible, depending on the data expressed in a field.

Content validation provides qualitative control of data values within a field, either in the form of a controlled vocabulary or through the use of masks. Controlled vocabulary content validation occurs when data within a field must conform to a predetermined set of terms, which are provided as a validation list. Validation lists are included within a database file where required, providing catalogers with a predetermined set of appropriate terms. Each validation list is exclusive to its respective field. For example, audio recordings are available in multiple formats, such as compact discs, vinyl LPs, vinyl 45’s, cassettes, mini discs, and 8-tracks, to name a few. Depending on the media within a collection, the presence of a format field with an accompanying format validation list is appropriate to provide both

Page 7: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 7

consistency from technical users at the time of data entry and consistency in the results provided to users at the time of query.

The North Texas Rock Music Appreciation Society’s database utilizes validation lists within four fields. Genre and Sub Genre possess validation lists to limit the terms available to technical users. The Content Warning field possesses a validation list of two terms, “yes” and “no”, to display the presence of a binary decision and to control potentially inconsistent entry practices. Finally, the Artist Nationality field possesses a validation list to create consistency in the entry of national origins and to prevent the use of generic origin terms such as “British”, “European”, or “Asian”.

A mask is a form of a content validation that requires catalogers to enter data based on a predetermined format. Often, masks are used with numerical strings in order to create consistency in data entry. Phone numbers, social security numbers, and dates are all examples of data that is controllable through the use of masks. Within the North Texas Rock Music Appreciation Society’s database the Date field utilizes a mask in order to create record to record consistency at the time of data entry.

A complete list of field types and validation types are found in Appendix B, Record structure and specifications.

2.4. Record content and input rules

Content and input rules exist to ensure the use of consistent information and input methods by catalogers in the process of data entry. Content rules specifically address what kind of information is entered by technical users, while input rules address the manner in which this information is entered. Such rules present a variety of specific instructions to a cataloger including the location of data about the entity and the exact method by which data is entered into a record.

Chief sources of information are selected by designers to provide technical users with consistent sources of data. While the actual sources used may vary from database to database, the concept of chief sources is common to the creation of consistent, high quality databases. A chief source of information can be a set of physical properties present on a collection object. The utilization of predetermined sources results in consistent data entry by limiting the potential for variation in the information gathered. If information is gathered from a number of disparate sources, the potential for data to vary from record to record increases, resulting in low quality search results for users of the system.

For the North Texas Rock Music Appreciation Society’s collection database there are two sources of information for catalogers to utilize, a chief source and a secondary source. The chief source of information gathered for the database comes from the actual objects that constitute the collection, in this case individual compact discs. Much of the container based information required is present on the compact disc, the compact disc packaging, or in the liner notes included with the compact disc. These fields are Artist, Member, Title, Date, Special Features, Content Warning, Producer, and UPC. The data necessary for catalogers to create these fields within a record is printed either on the compact disc or in the liner notes. Catalogers refer to this as the chief source of information for the fields listed.

Fields that do not draw from the compact disc or packaging are Genre, Sub Genre, and Artist Nationality. This content data is drawn from biographical and genre information for each artist found in individual Wikipedia articles, which serve as sources of information for these fields. While a field such as Artist Nationality sometimes requires further verification, the fields of Genre and Sub Genre are more problematic as subjectivity exists in the classification of stylistic distinctions between musical genres. Unlike printed materials, which have directly discoverable subject matter, music is organized by genre, which is a less rigorously defined manner for distinguishing musical styles. In the case of printed material, subject summaries are often present, providing the user or cataloger with direct reference to the content of the material contained within. Musical recordings are exceptional in this case, as they do not provide a direct reference to the style or genre to which they belong.

Page 8: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 8

For this purpose, this issue is addressed by settling on a source of information that provides reference to the specific genres and sub genres and the artists associated with each. Cataloging rules are present for the fields of Artist Nationality, Genre, and Sub Genre to address these concerns.

A complete list of input rules and their related semantics are found in Appendix C, Record content and input rules. Example records are provided in Appendix G, Sample records.

3. Access and authority control

Authority control facilitates the access to consistent data within an information system. Entry rules ensure consistent data, whereas authority control ensures consistent access and results. If users are unable to access data reliably, search results do not accurately represent the information contained within the file. By using authority control, designers steer users away from the use of incorrect terms toward correct terms through the control of names, subject matter, binary distinctions, and minor features. The use of content validation, thesauri, or name authority files assist in this process by providing reference points during the search process.

Authority control is applied in a number of ways; one method of exercising authority control is the utilization of content validation. Controlled vocabularies provide predetermined lists of terms that are appropriate to an access point. Thesauri are a form of subject authority control consisting of lists of authorized and unauthorized terms and indicate the relationships between the terms. Thesauri allow users to see the logical connections between subject terms, and provide users with appropriate search terms that yield consistent and complete results. Name authority files provide catalogers with pseudonyms, complete names, and nicknames, all of which are attached to an authorized name for use within an information system. Name authority files connect all works by a single creator, even when produced under different names, thereby facilitating the retrieval of accurate and complete results.

Within the system for the North Texas Rock Music Appreciation Society’s collection, there are several examples of the exercise of authority control. First, four fields exhibit the utilization of content validation in the form of controlled vocabulary. These fields are Genre, Sub Genre, Artist Nationality, and Content Warning. Of these, Genre and Sub Genre are the only access points utilizing a controlled vocabulary in the form of a content validation list. The Genre and Sub Genre fields also utilize a thesaurus in order to convey the relationships between the terms between the fields. Other fields that serve as access points are Artist, Member and Title. Access to the Artist and Member fields is controlled though the utilization of a name authority file. Since the Title and Classification fields have been designed with single entry validation, no authority control exists for these fields.

4. Representation of information content

4.1. Subject access

Subject access is the ability for users to access information through the content fields. Access to information in a system is performed through the utilization of access points. The creation of access points must be controlled in order to provide consistent access to data within the file. The potential for problematic situations is created when access points that are too broad in scope or too great in number are provided to the user. In this case, users have too many options, and often receive a small number of very specific results due to excessive search options. However, the creation of access points that are too few in number or too limited in scope has the opposite effect, resulting in many generalized results. While specific search options are appropriate for technical user groups, broader, simpler search options are often appropriate for the majority of a system’s users. Thus, a balanced approach to subject access is required of system designers.

Subject data is data that addresses the content of the object in a record. Subject data is the product of subjective analysis by catalogers and deals with the intellectual content of an object, and thus the record. The inclusion of subject data goes beyond stating the physical, or container features of an object, and

Page 9: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 9

allows objects with dissimilar container elements to share connections through a description of the common distinguishing intellectual features of the objects. Implementation of controlled vocabularies for the subject fields serve to standardize terminology as related to user search behavior. Terminology used in the controlled vocabularies conforms to widely accepted definitions known to members of the society and to the majority of rock music enthusiasts.

In addition to providing a clue as to the intellectual content of an object, subject data is used for the purpose of classification. The inclusion of subject data in the classification scheme allows collection organization based on the grouping of materials sharing similar subject matter. Subject data is contained in fields such as Genre and Sub genre.

In the system for North Texas Rock Music Appreciation Society, subject access is provided through the Genre and Sub Genre fields, both of which deal with essence of the object, rather than addressing the features that merely describe the object. In collections based on musical works, genre and sub genre are often used to describe the stylistic differences and commonalities between works. Users of the Society’s collection demonstrate this same type of behavior, describing their interest or preference for specific genres or sub genres of music, thus their search behavior reflects this. These fields, Genre and Sub Genre, also serve as the primary facets in the system’s classification scheme. Expressions of these fields are contained in the Classification field as coded information.

4.2. Thesaurus structure

Subject authority control is the management of subject terms within a collection’s file. Subject authority control is a product of authority control and subject representation, and addresses the method of providing subject access to users. In both the creation of a new system and the utilization of an existing system, subject analysis of collection objects must occur. In this process designers and catalogers study the objects in a collection to determine the content of the objects and the relationships shared by them. From this analysis and the subsequent creation of subject terms, subject authority control is applied in the form of thesauri and subject headings. Thesauri provide both users and technical users with the logical and hierarchical structure of subject fields. The thesaurus for a subject field steers end users toward the use of authorized subject terms, resulting in more accurate and more complete search results. The thesaurus assists technical users by providing a hierarchical list of authorized terms, unauthorized terms, and the relationships between terms.

In the North Texas Rock Music Appreciation Society system, the Sub Genre field is under authority control through the use of a thesaurus. While there are two subject fields within the system, Genre and Sub Genre, the Sub Genre field contains the greatest depth of intellectual content, and therefore is a more appropriate field for thesaurus implementation. Use of the Genre field, which consists of four top level terms, is inappropriate since there is a lack of depth among the terms. Terms contained in the thesaurus match the terms found in the controlled vocabulary of the file. While the controlled vocabulary provides a list of terms that are appropriate for use in records, the thesaurus provides technical users and end users with an external list of the relationships between the terms within the controlled vocabulary of the file. In this way, the thesaurus is a form of controlled vocabulary.

Thesauri are organized through the use of semantic relationships. Lists of terms are structured in a way that connects terms by displaying the nature of their relationship. There are three types of semantic relationships: broad and narrow terms; related terms; and the use of some terms as substitutes for others, or “use” relationships. Broad and narrow term relationships address a hierarchical relationship where the broad term (BT) expresses general content while the narrow term (NT) expresses a more specific use of the content. For example, “Metal” is the broad term while “Speed Metal” is the narrow term in a relationship relating to genre and sub genre. In a related term (RT) relationship, terms with similar content are connected in order to show an associative relationship. While the meanings of the terms are not the same, they address similar intellectual content. For example, “Post Prog” and “New Progressive” are related sub genres of rock music. “Use” relationships display equivalent relationships between terms. In the case equivalent relationships one term is selected as the authorized term and is “used for” (UF) unauthorized terms. An equivalent relationship indicates which term to use through the structure of the

Page 10: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 10

thesaurus. All relationships in a thesaurus must be reciprocal, displaying a one-for-one connection and the existence of appropriate relationships. Failure to reciprocate relationships between terms results in an ineffective thesaurus, which fails to serve both end users and technical users.

The domain of a thesaurus addresses the overall subject matter of the thesaurus, and is considered as the top level term, while the scope of a thesaurus addresses the depth of information presented to users. For the North Texas Rock Music Appreciation Society the domain of the thesaurus is the subject of rock music. The system is subject indexed through the Genre and Sub Genre fields, presenting users with the option to search the general subject terms of the Genre field, the specific subject terms of the Sub Genre field, or a combination of both. This system of indexing addresses the varying needs of the members of the Society.

Specificity is how well a subject term represents the intellectual content of an object. Specificity can be very broad, presenting users with generalized concepts, or it can be very narrow, presenting users with very specific concepts. Low specificity subject terms are appropriate for groups such as browsers and children; alternately, high specificity addresses power users and experts by narrowing the focus of the subject matter. The specificity for the North Texas Rock Music Appreciation Society’s collection is of a moderate level, since the need for broad genre terms exists alongside the need for more specific sub genre to address the content of objects within the collection. Consequentially, users of the collection are subject to greater recall of results or results that may be more precise than they desire. Regardless, this level of specificity is justified since the Society’s collection serves a user group of varying sophistication.

Exhaustivity addresses the breadth to which subject terms are connected to other terms. In highly exhaustive systems subject terms are connected to a large number of other terms and display a wide variety of semantic relationships. In systems that are less exhaustive in nature, subject terms share a small number of semantic relationships with other terms. While the exhaustivity of the North Texas Rock Music Appreciation Society’s collection is low, this is due to the existence of a set of generally agreed upon sub genre terms.

A complete thesaurus is found in Appendix D, Sample thesaurus.

4.3. Classification scheme

Classification provides users with the physical address of an object within a collection. Classification also conveys information about objects through coded systems that mirror the metadata underlying the record structure. Classification schemes assist in the physical process of collection organization. In a collection, users are served through the collocation of objects sharing common characteristics. Classification by subject is an effective way to collocate objects of similar intellectual content, and assists in directing users toward objects that meet their search goals.

Different classification schemes exist, with hierarchical and faceted schemes being most common. In a hierarchical scheme objects are classified based on a hierarchical structure. One example of this is the division of compact discs from vinyl pressed recordings, with the vinyl recordings divided further into LPs and 45 rpm categories. Hierarchical classification works well when organizing objects based on container based features. In a faceted classification scheme the objects of a collection are organized based on their intellectual content and expressing similarities between objects with differing container features. An example of a faceted classification scheme is the division of compact discs based on genre. The use of both hierarchical and faceted classification is appropriate for some collections, especially when media of differing formats are part of the same collection.

For the North Texas Rock Music Appreciation Society a faceted scheme is used. Since all of the objects in the collection share similar format, compact discs, the use of hierarchical classification is not appropriate. Major differences of intellectual content define the objects within the collection, thus a faceted scheme is used to address these content differences.

Page 11: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 11

The primary facet of the classification scheme for the North Texas Rock Music Appreciation Society is Genre, a subject field that provides general information about the content of an object. In the primary line of the classification scheme, Genre occurs first. Sub Genre is used as a secondary subject facet, in order to allow the organization of similar works within general genre groups. Finally, the Artist field contributes to the first line of the classification scheme. Inclusion of the Artist facet allows for further depth of organization within the sub genre division.

The second line of the classification scheme addresses container features of the object. The Date facet is the first facet of the second line and allows for the organization of objects by a single artist in chronological order. This is followed by the Title facet, allowing for alphabetical organization of titles contained within a particular year. Finally, the Content Warning code is attached to the end of the second line. The Content Warning code does not assist in the organization of objects, but instead provides an indicator to users of the presence or lack of a content warning for an object.

The third line of the classification scheme is the unique number for each object in the collection. Unique numbers are included in classification schemes to distinguish objects of similar characteristics from each other. In the event that two objects in a collection share features that result in identical classifications, the unique number provides a method of identifying each object as distinct from any others. Unique numbers vary from collection to collection, as each object in a collection is cataloged based on the needs of the collection. The call number for an object consists of the combination of the classification scheme and the unique number. The unique number for the North Texas Rock Music Appreciation Society consists of the last five digits of the UPC field in combination with a four digit version of the data contained in the RecordID field.

The following call number represents the album “Absolution” by the musical act Muse:

PS.NPR.MUS2003.ABS.n73327.0001

The first line consists of the Genre code “PS” for psychedelic, the Sub Genre code “NPR” for new progressive, and the truncated Artist name “MUS”. The second line consists of the Date “2003”, the truncated Title “ABS”, for “Absolution”, and the Content Warning code “n”, indicating a lack of a content warning. The unique number occupies the third line and consists of the last five digits of the UPC field, “73327”, and the four digit RecordID number “0001”, which indicates that this is the first record in the file.

A complete explanation of classification rules, appropriate codes, and an example are found in Appendix E, Sample thesaurus.

5. Name authority control

Name authority control exists to prevent confusion associated with creators using multiple names, varying name usages, and the use of pseudonyms. Name authority control assists in standardizing the method in which the names of people or named groups are searched within a file. Name authority control is an important part of a well designed system because it bundles information associated with seemingly different individuals with a single common creator. For technical users, objects in a collection that may seem unrelated because of different creator names are associated with each other, providing coherency to relationships between objects. For end users, name authority control connects users with objects in the collection that share a common creator or creators.

Authority control files consist of records that declare an authorized name and then connect variant names to the authorized name. For example, the musician Gordon Sumner is popularly known as Sting. In a record for works by this artist, “Sting” is the authorized name and variant names such as “Gordon Sumner” or “Gordon Matthew Thomas Sumner” are listed as variants that point to the correct authorized name.

Page 12: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 12

Users make use of name authority files when a name believed to be correct does not return the expected results. In this case, a user consults the name authority entry for the known name. If the name is contained in the file, the authorized name associated with the known name is presented for use in searching the collection file.The North Texas Rock Music Appreciation Society’s system utilizes a name authority file for the fields of Artist, Member, and Producer. Since some artists use stage names and some producers use pseudonyms, it is important to associate these popularized names with legal names, since legal names are often used for the identification of writing and publishing credit. The Artist, Member, and Producer fields contain names that conform to this need. Name authority control is not used for the names of musical acts consisting of multiple members since varying musical act names are often associated with differences in genre or membership. However, Artist field entries that consist of single individuals are subject to name authority control. For example, “The Beatles” would not be under the exercise of name authority control, while the solo artist “George Harrison” would.

The complete specifications, structure, and rules associated with the name authority file are found in Appendix F, Name authority file.

6. System evaluation and development

6.1. Evaluation plan

A system is only useful when it remains robust and flexible to the needs of users over time. Static systems only address the items already within the collection, and cannot adapt to the inclusion of new materials. Therefore, it is important to evaluate the efficacy of the system by studying the performance of the system based on real world use while constantly updating the system with new material. This is accomplished by studying user behavior, polling user satisfaction with a system, and by studying the results presented by the system when real world search behavior is applied.

The evaluation plan for the system will consists of two methods. The first method studies direct feedback from users of the system in the form of evaluation surveys. The second method studies the efficacy of the information retrieval system by analyzing system use and performance. While both segments of the evaluation will be conducted independently, it will be necessary to analyze the results of both surveys in relation to each other in order to develop and maintain the system.

User satisfaction:

User satisfaction is based on fulfilling desired recall and precision quickly and simply while offering materials that interest users of the collection. Quarterly, evaluators will be selected at random from the patrons of the North Texas Rock Music Appreciation Society. The selected patrons should form a balanced user group ranging from heavy users of the system to occasional users of the system. This selection process removes bias from users who are adapted to system layout and system search methods.

The first segment of the user satisfaction evaluation will consist of a five level Likert scale based survey. This survey will ask users to evaluate their experience with the system, specifically if presented search options are clear, intuitive in terms of use, and if returned results are consistent with intended search goals. Collection layout and the classification scheme will also be analyzed in order to ensure that users are acquiring the results of their searches with ease.

The second segment of the user satisfaction evaluation will be a free form comment field which will allow users to describe any likes or dislikes of the system, any examples of problems that they have with the system, or ideas to improve system performance and thereby improve user satisfaction. In addition to comments about the system, users are encouraged to suggest the inclusion of new sub genres or materials for expansion of the collection.

Page 13: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 13

IR system performance:

The second method of evaluation consists of studying the search terms entered by users. This data is used in order to study the effectiveness of name authority files, thesauri, and other subject control methods. If evaluators observe frequent use of genre or sub genre terms that do not conform to the subject authority controls, the validity or necessity of those terms will be analyzed and considered for potential inclusion in the system. One example of this is the emergence of a new sub genre of music that is not represented in the collection database, yet is gaining popularity or importance among users of the system. The music industry is constantly producing new products and as the collection grows these new products must be added to the system. Likewise, sub genres develop in a constant manner, so the inclusion of new sub genre data is necessary for the future efficacy of the system.

Note that users cannot be identified by entered search terms, so patron anonymity is preserved.

6.2. Performance test

A performance test was conducted with the listed user questions. The subject selected for the test is a 28 year old university educated female who is reasonably familiar with current and past musical acts. She possesses moderate domain and system knowledge, and displays high information seeking behavior. This user shares similar characteristics with users of the North Texas Rock Music Appreciation Society. Testing occurred in a residential structure on a home computer. Both the name authority file and thesaurus were presented with a cursory explanation of their use and purpose. Explanations of the basic functions of the database software were provided. No further instruction was given in order to simulate the experience of a new, untrained user accessing the system for the first time. No assistance was offered during the actual test session.

User question 1: “I am preparing a presentation on the Post-punk movement, and I need around seven to ten examples of musical works that developed out of this movement.”Object attributes: Genre.Desired precision: Low. The works are not asked for specifically, rather a range is necessary.Desired recall: High.Query formulation 1: The user searched Subgenre “Post Punk”.Probable precision: Low. Since the user searched with the top level term for the attribute in this query, few results which correctly address the question are expected.Probable recall: High. The simplicity of the query formulation is expected to result in a sufficient number of records returned. Analysis of results: The user retrieved one record, RecordID #8, “Head on the Door” by The Cure. While this record is part of the Post Punk subgenre, it is not a member of a subgenre that developed out of the Post Punk subgenre. This query formulation did not fulfill the goals of the user question.Query formulation 2: The user searched Subgenre “Alternative”. Probable precision: High. Because of the direct search of the subgenre term as found in the thesaurus, a small number of specific results conforming to one attribute are expected.Probable recall: High. The simplicity of the query formulation is expected to result in a sufficient number of records returned. Analysis of results: The user recovered zero records, as there are no records in the file matching this query. For this query formulation, the user consulted the thesaurus and applied the narrow Subgenre field term. The query formulation was sufficient to retrieve valid results in an actual setting and would have proved successful in a probable setting. Actual recall was not fulfilled due to the limited number of records in the test database, but probable recall would have been fulfilled by the user query. Actual precision fulfilled the user question, and probable precision would have been fulfilled by the applied query formulation.Query formulation 3: The user searched Subgenre “Gothic Rock”.Probable precision: High. Because of the direct search of the subgenre term as found in the thesaurus, a small number of specific results conforming to one attribute are expected.

Page 14: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 14

Probable recall: High. The simplicity of the query formulation is expected to result in a sufficient number of records returned. Analysis of results: The user retrieved one record, RecordID #4, “In the Flat Field” by Bauhaus. This album is of a subgenre that developed from the Post Punk subgenre. For this query formulation, the user consulted the thesaurus and applied the narrow Subgenre field term. The query formulation was sufficient to retrieve valid results in an actual setting and would have proved successful in a probable setting. Actual recall was not fulfilled due to the limited number of records in the test database, but probable recall would have been fulfilled by the user query. Actual precision fulfilled the user question, and probable precision would have been fulfilled by the applied query formulation.Query formulation 4: The user searched Subgenre “Indie Pop”.Probable precision: High. Because of the direct search of the subgenre term as found in the thesaurus, a small number of specific results conforming to one attribute are expected.Probable recall: High. The simplicity of the query formulation is expected to result in a sufficient number of records returned. Analysis of results: The user retrieved one record, RecordID #5, “The Queen Is Dead” by The Smiths. For this query formulation, the user consulted the thesaurus and applied the narrow Subgenre field term. This album is of a subgenre that developed from the Post Punk subgenre. The query formulation was sufficient to retrieve valid results in an actual setting and would have proved successful in a probable setting. Actual recall was not fulfilled due to the limited number of records in the test database, but probable recall would have been fulfilled by the user query. Actual precision fulfilled the user question, and probable precision would have been fulfilled by the applied query formulation.Query formulation 5: The user then searched Subgenre “Shoegaze”. Probable precision: High. Because of the direct search of the subgenre term as found in the thesaurus, a small number of specific results conforming to one attribute are expected.Probable recall: High. The simplicity of the query formulation is expected to result in a sufficient number of records returned. Analysis of results: The user retrieved one record, RecordID #2, “Loveless” by My Bloody Valentine. For this query formulation, the user consulted the thesaurus and applied the narrow Subgenre field term. This album is of a subgenre that developed from the Post Punk subgenre. The query formulation was sufficient to retrieve valid results in an actual setting and would have proved successful in a probable setting. Actual recall was not fulfilled due to the limited number of records in the test database, but probable recall would have been fulfilled by the user query. Actual precision fulfilled the user question, and probable precision would have been fulfilled by the applied query formulation.

User question 2: “I enjoy Industrial music, especially the album “The Downward Spiral” by Nine Inch Nails. Can you show me 3 or 4 more titles involving the same band members or producers?”Object attributes: Genre, album, producer, artist, band members.Desired precision: High. Not only is it necessary to identify the members and producers of the album “The Downward Spiral”, but it is also necessary to then find titles involving those same individuals.Desired recall: Moderate.Query formulation 1: The user searched Album “The Downward Spiral”Probable precision: High. The specificity of the search criteria should result in initial high precision results. Probable recall: Low. Expected returned results should be low since the user searched for a single album title.Analysis of results: The user retrieved one record which conformed to the results of the query formulation, RecordID #10, “The Downward Spiral” by Nine Inch Nails, produced by Trent Reznor and Flood. The query formulation was sufficient to retrieve valid results in an actual setting and would have proved successful in a probable setting. Actual recall was fulfilled in spite of the limited number of records in the test database, and probable recall would have been fulfilled by the user query as well. Actual precision fulfilled a portion of the user question, and probable precision would have also been partially fulfilled by the applied query formulation.Query formulation 2: The user searched Member “Trent Reznor”Probable precision: High. The specificity of the search criteria should result in initial high precision results.

Page 15: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 15

Probable recall: Low. There was potential that very few of the records will conform to the query formulation leading to a small number of returned results. A limited number of applicable records also resulted in low recall.Analysis of results: The user retrieved one record which conformed to the results of the query formulation, RecordID #10, “The Downward Spiral” by Nine Inch Nails, produced by Trent Reznor. The query formulation was sufficient to retrieve valid results in an actual setting and would have proved successful in a probable setting. Actual recall was not fulfilled due to the limited number of records in the test database, but probable recall would have been fulfilled by the user query. Actual precision fulfilled the user question, and probable precision would have been fulfilled by the applied query formulation.Query formulation 3: The user searched Member “Flood”Probable precision: High. The specificity of the search criteria should result in initial high precision results. Probable recall: Low. There was potential that very few of the records will conform to the query formulation leading to a small number of returned results. A limited number of applicable records also resulted in low recall.Analysis of results: While Flood is not a member of the band Nine Inch Nails, the user attempted a search because the Producer field was not indexed. This search did not retrieve any results and indicated that an error in system design exists due to the presence of a non-indexed Producer field. The query formulation was insufficient in the retrieval of valid results in an actual setting and would not have proved successful in a probable setting. Actual recall was not fulfilled due to none of the records containing Flood in either the Artist or Member field. Likewise probable recall would not have been fulfilled by the user query. Actual precision did not fulfill the user question, and probable precision would not have been fulfilled by the applied query formulation.

User question 3: “I’d like one or two psychedelic albums performed by British musicians after the 1970’s.”Object attributes: Genre, nationality of artist, copyright date.Desired precision: High. Not only does the user specify the nationality of the artist, but albums released after a specific date are required.Desired recall: Low.Query formulation 1: The user searched Genre “Psychedelic” and then parsed the results based on the information contained in the Date and Artist Nationality fields.Probable precision: Moderate. The specificity of the search criteria should result in high precision results, however, users will have to parse the overall results for results that match the search criteria since Date and Artist Nationality are not indexed. Manual analysis of records may result in error.Probable recall: Low. There is potential that very few of the records will conform to the query formulation leading to a small number of returned results.Analysis of results: The user retrieved three records based on the original query formulation, RecordID #1, “Absolution” by Muse, RecordID #2, “Loveless” by My Bloody Valentine, and RecordID #3, “Dark Side of the Moon” by Pink Floyd. Of these three results, only two fulfilled the criteria presented in the user question. All of the records retrieved describe artists of Irish or English nationality, which places them in the greater category of British bands. Of the records retrieved in the initial query formulation only two of the records refer to albums produced after the 1970’s, the exception being RecordID #3, “Dark Side of the Moon” by Pink Floyd, which was produced in 1973. For this query formulation, the user searched the Genre field to gather a global set of records and then eliminated the records that did not conform to the secondary parts of the user question. The query formulation was sufficient to retrieve valid results in an actual setting and would have proved successful in a probable setting. Actual recall was not fulfilled due to the limited number of records in the test database, but probable recall would have been fulfilled by the user query. Actual precision fulfilled the user question, and probable precision would have been fulfilled by the applied query formulation.

User question 4: “My parents don’t want me to listen to music with explicit lyrics. Can you show me some metal albums that I can listen to without getting in trouble?”Object attributes: Genre, content warning.Desired precision: Moderate. The user wants a variety of objects to choose from, but those objects must exhibit a specific characteristic.

Page 16: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 16

Desired recall: Moderate.Query formulation 1: The user searched Genre “Metal” and then parsed the results into records that did contain a content warning and records that did not contain a content warning. Probable precision: High. The specificity of the search criteria should result in high precision results in terms of genre, however, the user will have to parse the retrieved results for valid results that match the search criteria. This second step is necessary because the Content Warning field is not indexed. While manual analysis of records may result in error, in this case the content warning information is clearly and easily noted by users.Probable recall: Low. Once the results have been parsed by the user a low number of results conforming to the search criteria will remain.Analysis of results: The user retrieved three total records, RecordID #6, “Nevermind” by Nirvana, RecordID #7, “Follow the Leader” by Korn, and RecordID #9, “Are You Dead Yet?” by Children of Bodom. Of these three results, only one fulfilled the criteria presented in the user question. For this query formulation, the user searched the Genre field to gather a global set of records and then eliminated the records that did not conform to the second part of the user question. The query formulation was sufficient to retrieve valid results in an actual setting and would have proved successful in a probable setting. Actual recall was not fulfilled due to the limited number of records in the test database, but probable recall would have been fulfilled by the user query. Actual precision fulfilled the user question, and probable precision would have been fulfilled by the applied query formulation.

The system appears to be robust and effective in consideration of the user test. Vocabulary control appears to be robust when applied to the user test. The thesaurus is effective in drawing distinctions and displaying relationships to the user. The search fields offered serve the user with both basic and complex search options. Name authority files match and refer to information contained within main database records.

However, issues do exist with the overall efficacy of the system. As shown in user question 2, indexing of the Producer field is necessary for successful search results. It is a major failing that a user cannot search for the name of a producer. As the system is currently designed, users must sift through all potential records to effectively connect albums with common non-member producers. This does not serve the user in a convenient and effective manner.

6.3. Change and development

Significant development of the system is best aimed at the depth of indexing; however, there is a paradox related to the indexing of fields. Offering too few fields provides widely scoped results, while the potential for user confusion exists when an excess of indexed fields are offered. While the depth of indexing appears appropriate for the needs of potential users, there are opportunities to index other fields and reduce the back end work required of users. For example, users searching for Genre, Date, and Nationality attributes are only able to search using the Genre field, causing them to manually sort and eliminate fields that do not meet the criteria for the Date and Nationality fields. Likewise, users searching for information based on the Producer field must manually parse each record to find useful information. While offering a greater number of indexed fields would be a viable solution to this type of problem, the potential of limited valid results is also possible due to the use of too many search terms being simultaneously applied to a single search query.

A better way of implementing the Genre and Sub Genre fields would have been to eliminate one of the fields, and assume the term “Rock”, which is the current top level term, as the ultimate genre term with all other stylistic distinctions classified as sub genre entries. By implementing this type of change in the development phase, the system would have been more streamlined thereby eliminating an unnecessary field and would have created a sleeker system. This would also further reduce the chance for user error and remove a potentially complicating and confusing query environment.

As users of the North Texas Rock Music Appreciation Society’s collection enter and leave the Society the need for a relevant collection remains important. Newer generations of users will seek new materials in

Page 17: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 17

addition to needing access to older materials. New sub genres of music will develop and will need to be implemented along with existing genres and sub genres. As the system is designed now, the addition of new sub genres is constrained by the language of the thesaurus and the controlled vocabulary of the database. Expansion of the entry rules and authorized sources is necessary to make the system truly expandable at the technical user level.

Development of an organization system that allows for true chronological release of albums would be another positive development. In the current incarnation of the system, two albums produced in the same year may be classified and physically organized in non-chronological order due to the alphabetization of the title facet in the classification.

Inclusion of a field addressing the record label or labels responsible for publishing a musical work may be a worthwhile addition to the system. Some music connoisseurs prefer to study musical works within the scope of a single publishing label. A field of this nature would serve users with greater domain knowledge and high information seeking tendencies.

Page 18: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 18

Appendix A. Metadata elements and semantics

No. Element name Semantics1 Creator Individual artist, musical act, or individual musician within an act responsible

for audio recording.2 Title Identifying name of music work or album title.3 Date Copyright date of album.4 Subject The genre or sub genre used to describe the style or the musical

characteristics of an audio recording.5 Feature Features that distinguish a recording from a standard release version. For

example, Super Audio CD (SACD), gold disc, or the presence of multiple discs. Also refers to the inclusion or exclusion of an explicit content warning on CD case.

6 Nationality National origin of artist or musical act.7 Producer Person or persons credited as producers in liner notes.8 Identifier Unique numerical identifier assigned to an audio recording for retail use.9 Classification Unique identifier assigned to an object within the collection.

Page 19: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 19

Appendix B. Record structure and specifications

1. Record structure specifications

No. Field name Field type Indexing Entry validation Content validation

1 RecordID Autonumber — — —2 RecordDate Autodate — — —3 Artist Text Term, Word Required —4 Member Text Term, Word Required —5 Title Text Term, Word Required, single —6 Date Date — Required, single Mask min 1900 –

max 3000 ####7 Genre Text Term, Word Required List8 Sub Genre Text Term Required List9 Special Features Text — — —10 Content Warning Text — Required, single List11 Artist Nationality Text — Required List12 Producer Text — Required —13 UPC Number — Required, single —14 Classification Text Term Required, single,

unique—

2. Textbase structure

Textbase: J:\INMAGI~1\MAINCreated: 2/16/2009 7:14:42 AMModified: 2/27/2009 5:47:18 PM

Field Summary: 1. RecordID: Automatic ID Validation: single-only 2. RecordDate: Automatic Date(Both Date and Time,When Created) 3. Artist: Text, Term & Word Validation: required 4. Member: Text, Term & Word Validation: required 5. Title: Text, Term & Word Validation: required, single-only 6. Date: Date Validation: required, single-only, min 1900, max 3000, mask #### 7. Genre: Text, Term & Word Validation: required, valid-list 8. Sub Genre: Text, Term Validation: required, valid-list 9. Special Features: Text 10. Content Warning: Text Validation: required, single-only, valid-list 11. Artist Nationality: Text Validation: required, valid-list 12. Producer: Text Validation: required 13. UPC: Number Validation: required, single-only 14. Classification: Text, Term

Page 20: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 20

Validation: unique, required, single-only

Log file enabled, showing 'Artist'Leading articles: a an the Stop words: a an and by for from in of the to

Textbase Defaults: Default indexing mode: SHARED IMMEDIATE Default sort order: <none>Textbase passwords: Master password = '' 0 Access passwords: No silent password

Page 21: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 21

Appendix C. Record content and input rules

Field Name: RecordID.Semantics: Unique identifier for each record within the file.Chief Source of Information: Automatically generated by database.Input Rules: Automatically generated by database.Example: 1.

Field Name: RecordDate.Semantics: Date and time of record creation. Chief Source of Information: Automatically generated by database.Input Rules: Automatically generated by database.Example: 2/18/2009 8:43:52.

Field Name: Artist.Semantics: Name of the artist or musical act responsible for original audio recording.Chief Source of Information: Compact disc, compact disc packaging, or liner notes.Input Rules: Find the artist name and title located on the spine of the compact disc case. The artist name is typically located to the left side of any text on the spine. Confirm the artist name by checking for a corresponding name on the front face of the compact disc or on the cover of the compact disc liner notes. If there is no matching text on the front face of the compact disc or on the cover of the liner notes, check inside the liner notes for corresponding text. Enter the artist name into the “Artist” field as seen on the compact disc recording. For albums that have a number of different artists credited as performing individual songs on the same album, enter the term, “Various Artists” into the artist field. Confirm presence of name by checking the name authority file if the artist is an individual. Refer to Appendix F: Name authority file.Example: Nirvana.

Field Name: Member.Semantics: Name of artist or names of members of a musical act.Chief Source of Information: Compact disc liner notes.Input Rules: Search for names within liner notes. Look for phrases such as, “<Name of Artist or Band> is/are:”. Also, look for Individuals credited along with instrumentation or vocal performance. If the artist is a single individual, enter the same name as found in the artist field. Enter all member names into the “Member” field as found in the liner notes in the format of “First name, last name”. In the even of various artists present on a single album, enter the name of the individual artist or musical act in the “Member” field in lieu of the names of the individual members of each respective musical act. Confirm presence of name by checking the name authority file. Refer to Appendix F: Name authority file.Example: Peter Murphy.

Field Name: Title.Semantics: The name or title of an audio recording.Chief Source of Information: Compact disc, compact disc packaging, or liner notes.Input Rules: Find the artist name and title located on the spine of the compact disc case. The title of an album is typically located to the right side of any text on the spine. Confirm the album title by checking for a corresponding title on the front face of the compact disc or on the cover of the compact disc liner notes. If there is no matching text on the front face of the compact disc or on the cover of the liner notes, check inside the liner notes for corresponding text. Enter the title of the recording into the “Title” field as shown on the audio recording. Capitalize leading articles and non-article title words. Include any punctuation found in the title of the album.Example: Are You Dead Yet?.

Field Name: Date.Semantics: Date of copyright for the original audio recording.Chief Source of Information: Compact disc, compact disc packaging, or liner notes.

Page 22: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 22

Input Rules: Find the copyright date by checking the rear face of the compact disc packaging. Often the copyright date is included among the publishing and legal information. Alternate locations consist of the face of the compact disc, either along the outer edge of the compact disc or around the center spindle hole, or in the publishing and album credits located in the liner notes. Enter the date as found on the source in the “Date” field, formatting the date according to the mask of ####.Example: 1973.

Field Name: Genre.Semantics: Top level terms to describe the musical genre or genres that apply to an audio recording.Chief Source of Information: Wikipedia entry for the artist.Input Rules: Search the artist entry as found on www.wikipedia.org. Begin by finding the stylistic origins of the sub genre of the artist or musical act as stated on the right hand side of the entry page. Follow the stylistic origins link and successive links until a term matching the control vocabulary for the genre field is found. Enter the genre of the artist or musical act in the “Genre” field based on the options presented in Appendix D, Sample thesaurus.Example: Metal.

Field Name: Sub genre.Semantics: A term or terms which indicate fine distinctions and stylistic characteristics within a parent genre.Chief Source of Information: Wikipedia entry for the artist.Input Rules: Search the artist entry as found on www.wikipedia.org. The sub genre of an artist or musical act is commonly stated on the right hand side of the entry page and in the introductory paragraphs. Enter the sub genre of the artist or musical act in the “Sub genre” field based on the options presented in Appendix D, Sample thesaurus.Example: New Progressive.

Field Name: Special Features.Semantics: Declares the presence of physical features which distinguish a version of a recording from other recording of similar material.Chief Source of Information: Compact disc and compact disc packaging.Input Rules: Features are physically distinguishable by inspecting the compact disc or compact disc packaging. Among these features are multiple compact discs which constitute a single album, or gold recording media, which are apparent through visual inspection. Super Audio Compact Disc encoding is often stated on the rear face of the compact disc packaging. Note special features by declaring them in the “Special Features” field.Example: Multiple compact discs.

Field Name: Content Warning.Semantics: Declares the presence or absence of a content warning for explicit content. The presence of a content warning does not address the nature of the content, such as profanity or violent imagery, but only addresses the presence of explicit content within the recorded material as determined by the Recording Industry Association of America (RIAA).Chief Source of Information: Compact disc packaging.Input Rules: Content warning is noted on the front face of the compact disc packaging by the presence of a black and white sticker stating, “Parental Advisory Explicit Content”. Use the control vocabulary provided. The presence of a content warning results in an entry of “Yes” in the “Content Warning” field. The lack of a content warning results in the entry of “No” in the content warning field. Example: Yes.

Field Name: Artist Nationality.Semantics: National origin or origins of the artist of a compact disc recording.Chief Source of Information: Wikipedia entry for the artist.Input Rules: Search the artist entry as found on www.wikipedia.org. Artist nationality is commonly found on the right hand side of the entry page and in the introductory paragraphs. Enter the artist nationality or nationalities in the “Artist Nationality” field based on the options presented in the control vocabulary.

Page 23: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 23

Example: American.

Field Name: Producer.Semantics: Individuals credited as producers for a compact disc recording.Chief Source of Information: Compact disc liner notes.Input Rules: Find the producer name or names located inside the liner notes. Enter all names for individuals credited as a producer with the format of “First name, last name”. For artists listed as producers, enter the name of the artist as listed in the liner notes. Confirm presence of name by checking the name authority file if the producer is an individual. Refer to Appendix F: Name authority file.Example: Trent Reznor.

Field Name: UPC.Semantics: The unique numerical identifier assigned to a compact disc recording for retail identification.Chief Source of Information: Compact disc packaging.Input Rules: Locate the UPC on the back face of the compact disc packaging. Enter the UPC exactly as printed on the compact disc packaging, removing any dashes “-“ present.Example: 015775151727.

Field Name: Classification.Semantics: The unique identifier assigned to a record at the time of cataloging. Classification is used to detail the location of a compact disc recording within the physical collection.Chief Source of Information: Data contained within the record for a compact disc recording.Input Rules: Create the classification number as described in appendix E. Enter the classification for each object in the “Classification” field.Example:

PS.NPR.MUS2003.ABS.n73327.0001

Page 24: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 24

Appendix D. Sample thesaurus

BT = Broad termNT = Narrow termRT = Related term

UF = Use forUSE = Use

Italicized terms refer to Subgenre field entries.

Alt-RockUSE Alternative

AlternativeBT Post PunkNT GrungeNT IndustrialNT New ProgressiveUF Alt-Rock

Black MetalBT Death Metal

Death MetalNT Black MetalRT Melodic Death Metal

GothUSE Gothic Rock

GothicUSE Gothic Rock

Gothic RockBT Post PunkUF GothUF Gothic

GrungeBT AlternativeBT MetalNT Nu Metal

IndieBT Post PunkNT Indie PopNT New Progressive

Indie PopBT IndieBT Pop Rock

IndustrialBT AlternativeNT Nu Metal

Melodic Death MetalRT Death Metal

MetalNT GrungeNT Nu MetalNT Speed MetalNT Thrash Metal

New ProgressiveBT AlternativeBT IndieBT ProgressiveRT Post Prog

Nu MetalBT GrungeBT IndustrialBT Metal

Pop RockNT Indie Pop

Post ProgRT New Progressive

Post PunkBT PunkNT AlternativeNT Gothic RockNT IndieNT Shoegaze

Power MetalBT Speed Metal

ProgUSE Progressive

ProgressiveBT PsychedelicNT New ProgressiveUF Prog

PsychedelicNT ProgressiveNT Space Rock

PunkNT Post PunkRT Thrash Metal

ShoegazeBT Post PunkBT Space RockUF Shoegazer

ShoegazerUSE Shoegaze

Space RockBT PsychedelicNT Shoegaze

Speed MetalBT MetalNT Power MetalRT PunkRT Thrash Metal

Thrash MetalBT MetalRT PunkRT Speed Metal

Page 25: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 25

Page 26: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 26

Appendix E. Classification scheme

1. Scheme

Genre (code) Sub Genre (code) Artist Date Title Content Warning (code)Metal (ME) Alternative (ALT) (see

rules)(see rules)

(see rules)

Yes, content warning present (y)

Pop Rock (PO) Gothic Rock (GTR) No, content warning not present (n)

Psychedelic (PS)

Grunge (GRN)

Punk (PU) Indie (IND)Indie Pop (NDP)Industrial (IST)Melodic Death Metal (MDM)New Progressive (NPR)Nu Metal (NUM)Post Punk (PPU)Progressive (PRG)Shoegaze (SGZ)Space Rock (SPR)

2. Notation rules

Facet name: GenreChief source of information: Information for this facet is drawn from the Genre field of the record.Notation rules: Use the Genre code from the following table. Enter the Genre code in capitalized letters followed by a period. In the event that a record had multiple genre entries, use the term that occurs first in an alphabetized list.

Facet name: Sub GenreChief source of information: Information for this facet is drawn from the Sub Genre field of the record.Notation rules: Use the Sub Genre code from the following table. Enter the Sub Genre code in capitalized letters followed by a period. In the event that a record had multiple sub genre entries, use the term that occurs first in an alphabetized list.

Facet name: ArtistChief source of information: Information for this facet is drawn from the Artist field of the record.Notation rules: Use the first three letters of the artist name. Do not use articles when choosing the first three letters. Capitalize all letters in the Artist code. For example, for the artist “The Flaming Lips’ The Artist code is “FLA”, likewise the Artist code for “A Perfect Circle” is “PER”.

Facet name: DateChief source of information: Information for this facet is drawn from the Date field of the record.Notation rules: Begin a new line within the classification number. Enter the date of publication as found in the record for the Date code. Follow the Date code with a period.

Facet name: TitleChief source of information: Information for this facet is drawn from the Title field of the record.Notation rules: Use the first three letters of the title of the album. Do not use articles when choosing the first three letters. Capitalize all letters in the Title code. A period follows the Title code. For example, for an album with the title “Three Cheers for Sweet Revenge”, the Title code is “THR.”.

Page 27: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 27

Facet name: Content WarningChief source of information: Information for this facet is drawn from the Content Warning field of the record.Notation rules: Enter the Content Warning code as either a “y” or an “n”. Do not capitalize the Content Warning code. Do not follow the Content Warning code with a period.

3. Rule for unique number

The unique number for an object’s classification is created from the UPC field and the RecordID field. Begin a new line within the classification number. Enter the last 5 digits from the UPC field as the first portion of the unique number for a record. The last 5 digits of the UPC are followed by a period. Enter the data from the RecordID field in a four digit format. For example, if the RecordID is “5” for the fifth record entered, enter “0005” in the unique number portion of the classification.

4. Example

The 2003 album “Absolution” by Muse is a New Progressive musical work, which is a sub genre of the Psychedelic genre. This album lacks a content warning.

Based on the classification rules the following classification number applies to this musical work:

PS.NPR.MUS2003.ABS.n73327.0001

The first line consists of the Genre code “PS” for psychedelic, the Sub Genre code “NPR” for new progressive, and the truncated Artist name “MUS”. The second line consists of the Date “2003”, the truncated Title “ABS”, for “Absolution”, and the Content Warning code “n”, indicating a lack of a content warning. The unique number occupies the third line and consists of the last five digits of the UPC field, “73327”, and the RecordID number expressed as four digits, “0001”, indicating that this is the first record in the file.

Page 28: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 28

Appendix F. Name authority file

1. Record structure specifications

No. Field name Field type Indexing Entry validation1 RecordID Autonumber — —2 RecordDate Autodate — —3 AuthorizedName Text Term, Word —4 VariantNames Text Term, Word —5 SourcesUsed Text — —

2. Textbase structure

Textbase: J:\INMAGI~1\NAFCreated: 4/17/2009 2:56:08 PMModified: 4/17/2009 2:56:08 PM

Field Summary: 1. RecordID: Automatic Number(next avail=6, increm=1) 2. RecordDate: Automatic Date(Both Date and Time,When Created) 3. AuthorizedName: Text, Term & Word 4. VariantNames: Text, Term & Word 5. SourcesUsed: Text

Log file enabled, showing 'RecordID'Leading articles: a an the Stop words: a an and by for from in of the to

Textbase Defaults: Default indexing mode: SHARED IMMEDIATE Default sort order: <none>Textbase passwords: Master password = '' 0 Access passwords: No silent password

3. Record content and input rules

Field Name: RecordID.Semantics: Unique identifier for each record within the file.Input Rules: Automatically generated by database.Example: 1.

Field Name: RecordDate.Semantics: Date and time of record creation. Input Rules: Automatically generated by database.Example: 2/18/2009 8:43:52.

Field name: AuthorizedNameSemantics: Commonly used name of artist as found on album liner notes and as entered into Artist, Member, or Producer field of collection database.Input rules: Enter artist, member, or producer name into the “AuthorizedName” field as entered into the Artist or Member field of the collection database in the format of “First name, last name”. Example: Morrissey

Field name: VariantNames

Page 29: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 29

Semantics: A name or names that are not commonly used as a public identifier for an artist, member, or producer of a musical act. This includes full legal names.Input rules: Enter artist, member, or producer name into the “VariantName” field as found in the used source. A name or names may include middle names. Enter values in the format of “First name, middle name or names, last name”. Include any suffixes such as “Jr.”, “Sr.”, “III”, etc. Do not include prefixes.Example: Steven Patrick Morrissey

Field name: SourcesUsedSemantics: Source used for confirmation of a variant name or variant names.Input rules: Enter the title of the material or materials used. If a website is used, include the URL for the website.Example: http://en.wikipedia.org/wiki/Morrissey

4. Sample records

RecordID: 1RecordDate: 4/17/2009 14:58:07AuthorizedName: MunkyVariantNames: James Shaffer; James Christian ShafferSourcesUsed: http://en.wikipedia.org/wiki/James_Shaffer

RecordID: 2RecordDate: 4/17/2009 14:58:56AuthorizedName: FieldyVariantNames: Reginald Arvizu; Reggie ArvizuSourcesUsed: http://en.wikipedia.org/wiki/Reginald_Arvizu

RecordID: 3RecordDate: 4/17/2009 14:59:30AuthorizedName: HeadVariantNames: Brian Welch; Brian Phillip WelchSourcesUsed: http://en.wikipedia.org/wiki/Brian_Welch

RecordID: 4RecordDate: 4/17/2009 15:01:39AuthorizedName: Krist NovoselicVariantNames: Krist Anthony Novoselic II; Chris NovoselicSourcesUsed: http://en.wikipedia.org/wiki/Krist_Novoselic

RecordID: 5RecordDate: 4/17/2009 15:02:22AuthorizedName: MorrisseyVariantNames: Steven Patrick MorrisseySourcesUsed: http://en.wikipedia.org/wiki/Morrissey

Page 30: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 30

Appendix G. Sample records

RecordID: 1RecordDate: 2/18/2009 8:43:52Artist MuseMember: Matthew Bellamy; Chris Wolstenholme; Dominic HowardTitle: AbsolutionDate: 2003Genre: PsychedelicSub Genre: New ProgressiveContent Warning: NoArtist Nationality: EnglishProducer: Rich Costey; Paul Reeve; John Cornfield; MuseUPC: 093624873327Classification PS.NPR.MUS> 2003.ABS.n> 73327.0001

RecordID: 2RecordDate: 2/18/2009 9:01:54Artist: My Bloody ValentineMember: Colm O'Ciosoig; Balinda Butcher; Debbie Goose; Kevin ShieldsTitle: LovelessDate: 1991Genre: Psychedelic; PunkSub Genre: ShoegazeContent Warning: NoArtist Nationality: IrishProducer: Kevin Shields; Colm O'CiosoigUPC: 075992675925Classification PS.SGZ.MYB> 1991.LOV.n> 75925.0002

RecordID: 3RecordDate: 2/18/2009 9:04:24Artist: Pink FloydMember: David Gilmour; Nick Mason; Richard Wright; Roger WatersTitle: Dark Side of the MoonDate: 1973Genre: PsychedelicSub Genre: Space RockSpecial Features: Gold CDContent Warning: NoArtist Nationality: EnglishProducer: Pink FloydUPC: 015775151727Classification PS.SPR.PIN> 1973.DAR.n> 51727.0003

RecordID: 4RecordDate: 3/14/2009 20:18:46Artist: BauhausMember: Kevin Haskins; David Jay; Peter Murphy; Daniel Ash

Page 31: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 31

Title: In the Flat FieldDate: 1980Genre: PunkSub Genre: Gothic RockContent Warning: NoArtist Nationality: EnglishProducer: BauhausUPC: 652637001327Classification PU.GTR.BAU> 1980.INT.n> 01327.0004

RecordID: 5RecordDate: 3/14/2009 20:22:15Artist: The SmithsMember: Andy Rourke; Morrissey; Johnny Marr; Mike JoyceTitle: The Queen Is DeadDate: 1986Genre: Punk; Pop RockSub Genre: Indie PopContent Warning: NoArtist Nationality: EnglishProducer: Morrissey; Johnny MarrUPC: 075992542623Classification PO.NDP.SMI> 1986.QUE.n> 42623.0005

RecordID: 6RecordDate: 3/14/2009 20:26:04Artist: NirvanaMember: Kurt Cobain; David Ghrol; Chris NovoselicTitle: NevermindDate: 1991Genre: Metal; PunkSub Genre: GrungeContent Warning: NoArtist Nationality: AmericanProducer: Butch Vig; NirvanaUPC: 720432442524Classification ME.GRN.NIR> 1991.NEV.n> 42524.0006

RecordID: 7RecordDate: 3/16/2009 10:22:36Artist: KornMember: Johnathan Davis; Fieldy; Munky; Head; DavidTitle: Follow the LeaderDate: 1998Genre: Metal; PunkSub Genre: Nu MetalContent Warning: YesArtist Nationality: AmericanProducer: Steve Thompson; Toby Wright; KornUPC: 074646900123

Page 32: SLIS 5200: IOP Template, Spring 2008bkb0099.pbworks.com/f/IOP-5200-Final.doc  · Web viewThey can be indexed by word, indexed by term, or indexed by both word and term. Fields that

Baron / TXWI-C / p. 32

Classification ME.NUM.KOR> 1998.FOL.y> 00123.0007

RecordID: 8RecordDate: 3/16/2009 10:25:25Artist: The CureMember: Robert Smith; Laurence Tolhurst; Porl Thompson; Simon Gallup; Boris WilliamsTitle: The Head On the DoorDate: 1985Genre: PunkSub Genre: Post PunkContent Warning: NoArtist Nationality: EnglishProducer Robert Smith; Dave Allen; Howard GrayUPC: 075596043256Classification PU.PPU.CUR> 1985.HEA.n> 43256.0008

RecordID: 9RecordDate: 3/16/2009 10:43:05Artist: Children Of BodomMember: Alexi Laiho; Roope Latvala; Janne Wirman; Henkka Seppala; Jaska RaatikainenTitle: Are You Dead Yet?Date: 2005Genre: MetalSub Genre: Melodic Death MetalContent Warning: YesArtist Nationality: FinnishProducer: Anssi Kippo; Mikko Karmila; Children Of BodomUPC: 602498719114Classification ME.MDM.CHI> 2005.ARE.y> 19114.0009

RecordID: 10RecordDate: 3/16/2009 10:52:47Artist: Nine Inch NailsMember: Trent ReznorTitle: The Downward Spiral: Deluxe EditionDate: 2004Genre: PunkSub Genre: IndustrialSpecial Features: SACD, Multiple discs (2)Content Warning: YesArtist Nationality: AmericanProducer: Trent Reznor; FloodUPC: 602498647288Classification PU.IND.NIN> 2004.DOW.y> 47288.0010