Sai Latha Kolla

Spring 2021
INFO 5200 [002]
Draft 4

Comic Book Collection:

Information Organization

1. Project description

1.1. Collection and information objects

Comic Book Collection is the name of this collection. It is located in the ComicsClub, Brandon, Florida.
This club is formed in 1989 by a group of comic book lovers devoted to serving comic books, gaming and
toy fans for all their hobby needs! This club doesn't simply serve comic books but also meets each week
with different fans like taking votes from all the individuals on the new comics. This club regularly
conducts events such as Batman Day, 2nd Saturday Super Sidewalk, Free Comic Book Day.

This collection comprises more than 130,000 back-issue comic books belonging to a wide range of
genres such as manga, science fiction, superhero, fantasy, action among various others. This collection
bars nothing specifically. The club has a diverse and interesting collection of highly slabbed and
unslabbed comic books.

The Club holds auctions on a regular basis, including comics, toys, as well as other products which
assists the club in ensuring proper event timing, funding, and selection growth.

1.2. Users' demographics and knowledge

ComicsClub has started a Facebook page for the users which has 1561 followers and is growing as more
people join. The club with an extent of expansion in the all-out individuals and the user bunch additionally
comprises of non-club individuals who are keen on comics. The users are commonly in the age-gathering
of 10 to 25 years, generally middle school students (30%), high school students (40%), undergraduates
(20%), working grown-ups (10%), both male and female. Most users live in and around Brandon. Having
Universal Studios and Disney World around them builds their interest more in collecting comics.

The knowledge level is the degree of knowledge or capability one has towards some random zone. These
are partitioned into four types.

 General Knowledge is a broad understanding of a variety of topics rather than a deep

understanding of a single topic that improves over time. Since the majority of our users are
students attending school or college, they have a strong understanding of a wide range of topics
and rated as high knowledge level.

 Domain knowledge, as opposed to general knowledge, is knowledge of a particular topic. Experts

in a specific topic are used to describe users that have domain knowledge. Most of our users are
comic book lovers so they have high knowledge of comics.

 System knowledge is the potential that the user has to execute simple tasks on a computer. The
majority of the users listed here are members of a Comic club-created Facebook community who
have ample knowledge of social media and computers to be deemed competent. so, their
knowledge is considered high.
 Kolla / 002 / p. 2

 Information seeking is a tool for acquiring knowledge in both technological and administrative
aspects. The capability of information seeking grows with age. As of majority of users are in the
age cap of 15 to 30 years they are rated as having a medium to high knowledge level.

Ramifications of not building an information system

In the present constantly changing and fast-moving world, where user’s interests and requirements are
continually evolving, the clubs that would like to stay serious and keep on working at the exhibition levels
can only coordinate their user’s interests. A system needs to be designed for medium to high knowledge
levels for making user’s life easy to access their favorite comics.

1.3. Users’ problems and questions

Comic books have been popular since the 1800 s. This was not uncommon to see a single comic book
being read by both children and adults. Users are comic book fans who are very happy to read new
stories or continuations of previous stories. In one form or other, certain viewers would be drawn to the
main character. It's likely that the characters have motivated them. Comic books remain common in
today's world due to their appeal and excitement.

User question 1: Jerry Siegel and Joe Shuster's Lex Luthor Action Comics No. 23 is what I'm looking for.
DC Comics publishes Lex Luthor.
Object attributes: Publisher, Character-name, Authors, Title
Desired precision: High
Desired recall: Low

User question 2: I'm looking for a Comic book named Superior Spider-Man published by Marvel Comics
in Feb 2014.
Object attributes: Publisher, Title, Published date
Desired precision: High
Desired recall: Low

User question 3: The Gunsinger Born Battle of Tull by Stephen King is what I need. It was about Roland
Deschain, the last of the gunslingers, resuming his quest for the Man in Black.
Object attributes: Title, Author, Character-name, Genre
Desired precision: High
Desired recall: Low

User question 4: Fight Club 2 Ashcan Edition is what I'm looking for. It's a Chuck Palahniuk story. Dark
Horse Comics Published it in 2015.
Object attributes: Title, Edition, Publisher, Published date, Real-Life Adaptation
Desired precision: High
Desired recall: Low

To summarize, users asked questions with various attributes such as Title, Genre, Character-name,
Author, Publisher, Published date and Real-Life Adaptation. All of which aid some users in their search.
There are other attributes such as Page Count, Cover Photo, Genre which also help users with their
search.

2. Representation of information objects

2.1. Entity level

The grouping of things with the same data in common is called an entity. A group of objects can be
represented by an entity. For instance, the Comic Book series is an entity. Entity level is an attribute that
 Kolla / 002 / p. 3

helps in capturing the object in a database by gathering the required information. Here one of the books in
the comic book series is featured as entity level. Metadata tells us information about one or more
attributes, making it easy to capture data in the database. To select which metadata to use to represent
the object, we must first choose the entity level. Users search this database for objects by including
information about the entity level. For instance, Author is one of the objects in this database by giving his
information one can find the book.

2.2. Metadata elements and semantics

Metadata tells information about one or more attributes, making it easy to capture data in the database.
Metadata is generated and stored to make data easy to access. Elements are a category of descriptive
metadata that includes data about a property. These 11 elements likewise uphold the four primary users’
tasks - Find, Identify, Select and Obtain.

Find user job is where a user attempts to identify an entity as a result of a search using an attribute of the
entity. It’s the first task of the user. The second user task Identify is to recognize an entity using the
information collected by the find task and to ensure that the entity mentioned in a database fits the one
requested by the user. The third task is Select which the user uses to pick an entity that is suitable to the
user's needs. The final user task is Obtain which helps to gain access to the entity mentioned by using
the information given.

The tasks Find and Identify are fit for the Author element so they can be used to search for the object and
verify what the user needs. The element Title can uphold three user tasks like, Find, Identify and Select,
as this element can be utilized to look, affirm and pick if the object of user’s fulfillment. Element Subject is
supported by the task Select, which allows users to choose from the results that best fit their needs. Real-
Life Adaptation is a part that aids in the user task Find. Genre is another element that underpins the
undertaking of Find and Identify as they can likewise be useful in looking through the collection and
confirming the outcomes looked. Page Count is another element that aids in the select task, since the
overall amount of pages aids in deciding the size of the object and is possibly a key factor for users
obtaining it. While the elements Published Date, Publisher, and ISBN are not needed for any of the user
tasks, they are useful for the cataloguer to keep track of them. Since it is used to physically locate the
object, the element Classification helps the Obtain task.

The elements discussed above, as well as their semantics, are described in Appendix A.

2.3. Record structure and specifications

Database becomes understandable with database specification. There are 11 fields in this database.
Each element maps one-to-one to a single field. There are five specifications for each field in this
database, they are Field Type, Required, Searchable, Controlled Vocabulary and Drop-Down Menu.

The Field Type demonstrates the arrangement of the information that is to be entered in the field, which
could be either alphabetic or numeric or alphanumeric or even blended organization in with special
characters. The Required particular tells the cataloguer if the field is required or not. On the off chance
that the field is required, the cataloguer can't leave this field unfilled. Searchable demonstrates if the field
can be available by the user during their inquiry. All in all, a Searchable field helps clients during their
information object search. A Controlled vocabulary is a cycle of utilizing a particular term to demonstrate
the subject of the information object. This aids in diminishing the information irregularity during the
information recovery. Drop-Down Menu gives the cataloguer choices by giving the rundown. Choosing
from this rundown of choices is the lone alternative to fill the field.

The Field type for the field Author is Text. The cataloger mandatorily needs to enter data as users need to
know the authors of the comic that they are reading. Since comics have several authors, the number of
terms allowed is limited to three words. A controlled vocabulary and a drop-down list are not available for
this field. Since an author's name cannot demonstrate a field's subject, and since there are several
 Kolla / 002 / p. 4

authors in this world, it cannot be restricted to a drop-down menu. Yes, it is a searchable field as users
look for comics by their writers.

The Field type for the field Title is in a blended configuration of Text format, as it contains alphabets and
numbers. For instance, Fight Club 2 Ashcan is a Dark Horse Comic released in 2015. The cataloger
mandatorily needs to enter data as users need to know the title of the comic that they are reading. The
title field is restricted to one term as every book has only one title. A controlled vocabulary and a drop-
down list are not available for this field. Since the title name cannot demonstrate a field’s subject and
there are a lot of comics in this world, it cannot be restricted to a drop-down menu. Yes, it is a searchable
field as users look for comics by its Title.

The Field type for the field Subject is Text. The cataloger needs to fill it in since the user needs to know
what the comic is about. Since comics have several subject terms, the number of allowed terms is limited
to five words. For instance, Brave, Science, College, Superheroes, Biography. A controlled vocabulary
and a drop-down list are not available for this field. Since a single term cannot be used to describe the
whole comic and there are a lot of subject terms that cannot be restricted into a drop-down menu. Yes, it
is a searchable field as many users know the subject of the comic they are looking for.

The Field type for the field Plot is Text. Since most comic books don't have a plot on the cover, the
cataloger may leave it blank or fill it in. As the whole story is can be pictured in a single view, the number
of terms is limited to one. A controlled vocabulary is not available for this field and drop-down menu is not
needed since this is a summary. It isn’t searchable as users do not have to know what the comic book
plot is about.

The Field type for the field Genre is Text. The cataloger needs to fill it in since the user needs to know
what genre the comic is belongs to. Since comics have a lot of genres, the number of allowed terms is
limited to 10. A controlled vocabulary is not available for this field because comic books can sometimes
belong to more than one genre. It has a drop-down menu with 10 significant genres such as Drama,
Horror, Mystery, Love, Romance, Comedy, Adventure, Thriller, Suspense and Fiction which are
preselected. Yes, it is a searchable field as many users already know the genre of the comic they are
looking for.

The Field type for the field Page Count is Numeric. The cataloger may leave it blank or fill it in since the
page count doesn’t really matter from the user’s perspective. Since each book has a specific number of
pages, only one word is permitted in this area. A controlled vocabulary and a drop-down list are not
available for this field. Since page number doesn’t demonstrate the subject of the book and doesn’t need
a drop-down menu. It isn’t searchable as users do not have to know about this.

The Field type for the field Cover Image is Picture format. The cataloger may leave it blank or fill it in
since the cover image doesn’t really matter from the user’s perspective. This field is restricted to one term
as every book has only one image. Controlled vocabulary and drop-down menu are really needed for a
picture. It isn’t searchable as users cannot search with a picture.

The Field type for the field Published Date is Numeric. The cataloger needs to fill it in since the user
needs to know in which year the comic is first released to keep up with the edition. A controlled
vocabulary is not available for this field. It has a drop-down menu that ought to be accessible in
YY/MM/DD which helps to pick a specific date. Yes, it is a searchable field as many users already know
the Published date of the comic they are looking for.

The Field type for the field Publisher is Text. The cataloger needs to fill it in since the user needs to know
who published the respective comic. The publisher field is restricted to one term as every comic has only
one publisher. A controlled vocabulary and a drop-down list are not available for this field. Since the
publisher name cannot demonstrate the object’s subject and there are a lot of publishers that cannot be
restricted into a drop-down menu. Yes, it is a searchable field as many users know the publisher of the
comic they are looking for.
 Kolla / 002 / p. 5

The Field type for the field ISBN is Numeric. The cataloger may leave it blank or fill it in since the ISBN
doesn’t matter from the user’s perspective. The ISBN field is restricted to one term as every comic has a
unique 13-digit code. Controlled vocabulary and drop-down menu are not needed for an ISBN field. It isn’t
searchable as most users do not know the ISBN number of a comic.

The Field type for the field Classification is in a blended configuration, as it contains alphabets and
numbers. The cataloger may leave it blank or fill it in since the classification doesn’t really matter from the
user’s perspective as that is used to locate comics physically. Controlled vocabulary and drop-down menu
are not needed for a classification field as each comic classification code is unique. It isn’t searchable as
most users do not know the Classification code of a comic.

The fields discussed above, as well as their Record structure specifications, are described in Appendix B.

2.4. Record content and input rules

A set of instructions and guidelines for the cataloguers on the best way to enter the information in the
fields is defined as Input rules. These guidelines assist the users with looking for the Information object
with no disparities during the search and it likewise helps cataloguers in keeping up this consistency all
through the cycle of information entry by reducing the replication of the information objects.

The data source that must be used to classify the object being mentioned is defined as the chief source of
information. Here, the chief source of information for comic books is the title page. The majority of fields
are located on the title page. Regarding problematic aspects in this one is that most of the comic books
miss descriptions and they can be found on the web in Comicsclub.com.

For the complete overview of input rules please refer to Appendix C.

For Sample Database Records Please refer to Appendix G.

3. Access and authority control

The process of arranging data in a database such as names and subjects is done by using authority
control. It can be applied to any collection of data. Its main purpose is it guarantees data integrity and
improves resource collocation in the catalog. It is critical to use authority control to simplify the types of
search words and maximize the probability that the search return the objects that the user needs.

The below are some of the advantages of providing specific access points under authority control for both
the users and catalogers.
Improved Search for users: It helps the users to enter a limited number of words in a database to
retrieve an already known term, increasing precision and efficiency.
Flexibility for catalogers: Catalogers use authority control documents that have already been
documented while trying to assign new objects into specific categories saving time.

Two types of authority control are present. One is Name authority control which means when a person's
name is used in the field, name authority control is used. Second is Subject authority control which means
the authority control is applicable to a subject field. It also has three mechanisms to follow one is Name
authority file which manages all fields with actual names. The fields Author, Publisher comes under this
name authority file. Second is a validation list which takes care of all the valid terms that are to be entered
into the database. Tags (Genre)field is an example of Validation list in this database. Third mechanism is
Thesaurus which incorporates the advantages of synonym sets with the inclusion of new elements. Tags
(Subject)field is an example of Thesaurus in this database.

If an access point is created under authority control it must be under some form of authority control.
Controlled vocabulary is a cycle of utilizing a set of terms to demonstrate the subject of the information
object that are listed in the subject authority file. The sub fields under Tags (Genre and Subject) field have
 Kolla / 002 / p. 6

the largest number of possible words, as well as the most complex terms and also these terms are related
to each other, so this tags field comes under thesaurus.

4. Representation of information content

4.1. Subject access

Subject representation is a process where the intellectual content of primary information objects is defined
by secondary information objects. Here secondary information objects are the subject representations
which helps in searching those primary information objects. Secondary information objects are only used
in conjunction with primary information objects and cannot be used on their own. This is where subject
analysis takes over.

The process of assessing and finding the intellectual content of an object is defined as subject analysis.
It is performed on both types of objects (documents and queries). Examining a document and determining
what indexing terms can be used to reflect in a record is how subject analysis is performed with
documents. Natural language indexing is used to represent this analysis, that involves choosing a
language which is commonly used by the user community throughout analysis, based on the subject field.
This natural language helps to authorizes the terms to use. It is done as part of the cataloging process.
Examining an information request and figuring out how to select suitable search words is how subject
analysis is performed with Queries. It is performed when designing a database from the user's
perspective (how users search for information objects).

Access usable for subject searching is known as subject access. This is where subject representation
does help. This system includes subject-related details in the Tags (Genre & Subject), and Plot.

The examination of similarities between objects is used to make a classification. Here a subject based
classification method is used since the subject has the greatest number of possible words and the terms
are related to each other and makes classification easier. Facets are various types of classes that help to
arrange objects. This system uses the Tags field as the subject-based facet in the classification scheme.

4.2. Thesaurus structure

Subject authority control is a process used in cataloging subject analysis sections. It guarantees that
names and subject headings in this collection are consistent and accurate. Subject authority files are
used to get the authority control on Subject fields. These subject authority records have controlled
vocabulary that helps in the representation of subjects. Subject authority files help in cataloging by
serving as a source of index terms and it also helps in searching by serving as a source of search terms.
As these serve for both cataloging and searching, they serve both end-users and technical users of the
system. To prevent misunderstanding and repetition with related subjects the tags field requires authority
control.

There are two types of subject authority files one is thesauri and the other is subject headings lists.

Here in this collection thesaurus is used as the subject authority file. Thesaurus incorporates the
advantages of synonym sets with the inclusion of new elements. It is a relational database of distinct
terms that includes synonym relationships. Thesaurus can also be referred to as a controlled vocabulary
organized in a defined pattern, shown with uniform relationship markers that are commonly used for
cataloging in information storage and retrieval systems. Subject headings lists are a collection of
standardized terms that are allocated to files to identify the files' subject and group them together with
other files on the same topic. Catalogers make use of Subject headings lists.

Thesaurus is a network of specific terms that are semantically linked. Its syndetic structure helps to
organize the relationships between those synonym subject terms and the manner in which new subject
terms are cataloged. Equivalence (synonym), hierarchical (genus/species), and associative are the three
 Kolla / 002 / p. 7

categories of semantic relationships found in the thesaurus. Mandatory reciprocals are used as a second
reference for the first term. A reciprocal's significance lies in reducing data duplication during cataloging.
Authorized terms are terms that are explicitly allowed in the controlled vocabulary whereas unauthorized
terms are ones that are not allowed.

Equivalence relationships can only be created between words and terms which have a true similar sense.
USE keyword is used to define equivalence relationships and UF for its mandatory reciprocal.
Hierarchical relationships can be created for a broader keyword that has a set of narrow keywords.
Consider a Genre. It has so many sub-genres that come under it. BT is used to define Broader keyword
(Example: Genre) and NT is used to define Narrow keywords (Example: Sub-genres). Associative
relationships can be created between words or terms that are related but not a synonym or a narrow term
under it. RT keyword is used to define an associative relationship.

The overall theme expressed in the controlled vocabulary is referred to as a domain. The domain's scope
refers to its limits in this collection. For this collection, both are the same. Here The domain and scope of
the collection is the Tags field (Genre & Subject) of comic books.

Specificity refers to the system's ability to retrieve appropriate words. Higher specificity extracts terms that
are similar to the subject representation, whereas lower specificity does not accurately include those
terms. When specificity is high, precision is high, and recall is low. For this collection, moderate Specificity
is considered to have moderate recall and precision.

The degree to which a cataloger describes the subject terms contained in an information object of the
collection is referred to as exhaustivity. Here low exhaustivity is used for indexing to decrease the recall of
the search. The method of providing a precise subject representation is known as depth indexing.
Summarization, on the other hand, presents the subject in a concise manner. Here the indexer should tend
more toward depth indexing as recall will be moderate due to its precise subject representation. For this
collection, moderate exhaustivity is considered to have moderate recall and precision.

4.3. Classification scheme

The method of structured grouping or categorizing objects based on existing parameters is called
classification and the explanatory material for arranging or grouping objects based on shared
characteristics is called a classification scheme. It helps both the users and catalogers in this system.
With the help of a predefined scheme, catalogers can easily arrange the existing collection and also can
easily add new items to the collection. Users can easily locate the books from the collection which saves
time.

There are 2 kinds of approaches to classification. One is the Hierarchical Approach and the other is
Faceted Approach. In a hierarchical approach, subjects are grouped into categories ranging from general
to specific. They are grouped into hierarchical classes and sub-classes before they are used. In this kind
of approach, further revisions like adding classes can be made with much difficulty to the system. It is a
common use-case for large collections as It's thought to be pretty simple to use, and it covers a vast
variety of topics with just a few subjects. Faceted classification employs a general or subject-specific
semantic division, which is then merged to form the complete classification entry. In the scheme classes
and sub-classes are not added ahead of time. This is a flexible scheme and further revisions can be
made to the system.

Facets are fixed permitted terms which are used to specify attribute. In this classification system a faceted
approach is taken as the schemes are flexible and not every facet needs to be used to create the
collection. Since this collection will increase as more books join so we have the flexibility to add new
classes to this scheme. Here the facets are chosen for this scheme are Genre, Published Date, Title. A
primary facet is one that specifies the classification scheme's key attribute. The primary facet here is
Genre. Since there is a small range of genres available, the whole set can be conveniently categorized by
splitting it into genres followed by Published Date. Published Date helps really well as the divided
 Kolla / 002 / p. 8

collection can be split into the year of release narrowing the collection even further and then followed by
Title. An additional facet ISBN is used from the last 3 digits of its number as a unique identifier if needed.

This classification scheme has a complete example with coding below. It comes from the collection.

Classification code: Thr2015Fig458

Primary Facet: Genre: Thriller (Thr)
Secondary Facet: Published Date: 02-15-2015 (2015)
Third facet: Title: Fight Club 2 Aschan Edition (Fig)
Unique identifier: 9781616559458 (458)

5. Name authority control

The method of selecting one approved type of data entry to ensure continuity in its usage is known as
name authority control. It emphasizes people's and organizations' names. It's important because it can be
extended to different database access points. These access points serve as an authorized term of data
entry for technical users when they are trying to catalog the database and also help the end-user to
search for the entry that he needs.

A document that supports the primary database or information retrieval system is called a name authority
file. It also contains a few key details regarding the entry to ensure the name being indexed is the same
as the one represented by the authority record. The cataloguer is given a list of approved words. If those
do not fit what is in the name authority file, it's up to technical users to upgrade and extend the name
authority file, or else they consult the name authority file. Also, it assists end users in locating suitable
types of names for searches as they already know the people's and organizations' names. Here in this
system Author field and Publisher field is under name authority control because name authority control
emphasizes people's and organizations' names.
https://www.loc.gov/catworkshop/courses/nametitleauth/pdf/Name-Title_Instr_Manual.pdf

For the complete overview of name authority file please refer to Appendix F.

6.0. System Evaluation

6.1. SWOT

SWOT analysis is an essential assessment system developed to examine the organization's competitive
role in its field of operation. It can be used to evaluate any situation or setting, from the development of a
web to the leadership of a global organization due to its analytical simplicity. SWOT analysis is a
technique for analyzing an organization's internal and external trends by identifying and evaluating its
strengths and weaknesses, threats, and opportunities.

In the account of SWOT, the Strengths segment refers to the benefits that a specific business or
organization has over all other businesses or organizations of the same kind. One of its strengths is
having a detailed classification scheme which helps catalogers to catalog easily and also it has a name
authority file which helps the technical users to upgrade and extend the name authority file by having a
name authorized record. Having these name authority records helps end users also benefit with their
searching.

In SWOT analysis, weaknesses refer to all the factors, both internal and external, that have the potential
to influence the development of an organization negatively. In this system, the fields Genre and Subject
are under the same Tags field which might be confusing to the cataloger to select the right attribute. Also,
the Genre filed under tags does not have a drop-down list in libib to select a genre.
 Kolla / 002 / p. 9

The term opportunities in SWOT analysis refers to external elements or an organization possibility that
contribute positively to organization development. Since this collection is also present in a website named
comicsclub.com so the website URL can be shared in the libib. An interactive can also be added to the
libib so that users can easily search for the book in the libib itself. Also, we can create separate fields for
Genre and Subject to avoid confusion to the users.

Threats in SWOT analysis refer to all factors that could damage the organization's performance, among
other aspects. Once the organization identifies potential threats, it works swiftly to address them through
various measures. External effects are referred to in the SWOT review as something that may have a
negative impact on companies or organizations. The tags field can be a threat as it raises confusion in
end users differing between Genre and Subject. Also, since every comic book is now available online no
one visits physical store collections.

SWOT Analysis Chart:

SWOT chart

Strengths Weaknesses

1. Detailed Classification Scheme 1. Important fields like Genre, Subject are

2. Name authority file helps to Upgrade
and extend the database.
3. System is easier for catalogers to
catalog and end users to search
Opportunities
not present in the libib.
2. Tags field will be confusing to the
catalogers while classifying.
3. No drop-down list for Genre in the libib.
Threats

1. Collection can be linked to the online
Comicclub URL.
2. User interactive to the comcisclub
website can be added to libib
3. Fields like Genre, Subject can be added
to the libib.
1. Tags field can cause a confusion to the
catalogers while classifying.
2. High availability of online comics can
cause less visits to the physical
collections.

This system has several advantages that paint a clear picture of its operations. However, the system has
flaws that can be addressed over time. The system has several opportunities that aid in its development
as well as provide justification for its presence. The opportunities also provide a clear picture of what
should be maintained in perspective as the system grows. The threats identify the reasons that must be
addressed as rapidly as possible, as they are the core issues that may affect the organization negatively.

PEST Analysis:

The acronym PEST stands for political, economic, social, and technological analysis. This research helps
to evaluate the impact of these four external factors on the system. In a nutshell, a PEST study aids in
assessing these aspects if they can impact the collection in the future.

Government policies and labor laws are evaluated in Political analysis for their potential to influence the
system and its market. Since this collection is maintained by comic club members there won't be any
political influence on the system.

Economic Analysis is a factor that talks about how a system affects due to factors like interest rates,
inflation, funding, and whenever money is involved. This system is funded by its own like this club
regularly conducts events such as Batman Day, 2nd Saturday Super Sidewalk and raises money in those
events. Also, The Club holds auctions on a regular basis including comics, toys, as well as other products
which assists the club in ensuring proper funding.
 Kolla / 002 / p. 10

Social Analysis tells us about user behavior and education, a system can evaluate the social and
economic condition of its market through social research. Since the majority of the club members are
connected via a Facebook page which has 1561 followers and is growing as more people join. They have
a high system knowledge so; the club members expect a more integrated database that helps them with
the club’s official website information in the libib itself.

Technological analysis tells us about how technology can impact the system. It is assessed here. By
using technology, one can upgrade the system. Having already an official website for the club helps the
end-user in finding the required comic book in no time. More technological advancements can be made to
the database so that it can be more user-friendly. Fields like Genre and Subject can be added to the
database. A comicsclub app can be created for the phone so that everyone can access the system from
their phone and libib system can also be integrated into this app.

PEST chart

Political Economic

 Political factors do not affect this system  Club receives its funding by holdng
as it is run by club members. auctions.
 Club also receives funding by conducting
regular events.

Social Technological

 Club members are growing as more
people join.
 Members are already Facebook page
followers, so they have high system
knowledge.
 Club members expect an integrated libib
database that makes the system more
user friendly.
 High availability of online comics can
cause less visits to the physical
collections.
 Upgrade needed to the database.
 An app can be created with comicsclub
and libib integrated.

6.2. Change and development.

This system has several advantages that paint a clear picture of its operations. However, the system has
flaws that can be addressed over time. The system has several opportunities that aid in its development
as well as provide justification for its presence. SWOT provided a clear picture of what should be
maintained in perspective as the system grows.

There are a lot of upgrades and changes needed in the libib database. There need to be user customized
fields in libib as every system has its own custom fields. Also, a lot of fields are associated with the Tags
field rather than having their own field. Having Tags field creates confusion to catalogers.

The comicsclub can integrate their collection with marketing giants like amazon and a lot of comic book
lovers across the world can easily get access to the collection. Also, Comicsclub app integration with libib
app creates a more user-friendly interface to the end users making their search very simple.

Also, drop-down lists in libib helps for fields like Genre and Subject which have limited terms. User can
then easily check the drop-down list and select the term rather than keep thinking about it.
Libib should have a drop-down lists for fields like Genre and Subject, which have a limited number of
terms. In this case, the user can easily select the term by looking at the drop-down list.
 Kolla / 002 / p. 11

7.0. Project summary

I picked a comic book collection because it is one of my childhood favorites. It turned out to be an
acceptable collection size for this project. It was not easy building this system from scratch earlier for me
but the kind of learning material and the assistance from the professor’s helped a lot.

Designed a library and database gave me a better understanding of how a perfect system could function.
This has made me understand what factors could be considered to create a system with will be easy for
cataloging and searching. It may not be perfect at this point but with technology and time, one can build a
perfect system.

When it came to portraying the objects in this collection, I had no big issues. Despite the fact that it is
lengthy and time-consuming. But this project helped me improve my vocabulary, Punctuation at the same
time teaching me how to create a database traditionally and in libib. Creating records in libib was easy
and fun. I gained useful knowledge that can be used to improve the database better for both the
catalogers and end-users.
 Kolla / 002 / p. 12

Appendix A. Metadata elements and semantics

No. Element name Semantics

1. Author Person who created the information object.

2. Title The word or an expression given to the information object.

3. Subject Main theme the information object is based on.

4. Plot A short depiction of the story.

5. Genre The nature of a information object determines which class it belongs to.

6. Page Count The absolute size that establish the story.

7. Cover Image The Pictorial representation of the object.

8. Published Date The date on which the information object is published

9. Publisher The business that makes the information object open to the general public.

10. ISBN An identifier that is supposed to be one-of-a-kind to identify information

object.

11. Classification A unique code that is supposed to be one-of-a-kind to identify information

object physically.
 Kolla / 002 / p. 13

Appendix B. Record structure and specifications

1. Record structure specifications

No. Field name Field type Searchable Required Number of Controlled Drop Down
allowed Vocabulary? List?
entries

1. Author Text Yes Yes 3 No No

2. Title Text/ Yes Yes 1 No No

Numeric

3. Subject Text Yes Yes 5 No No

4. Plot Text No Yes 1 No No

5. Genre Text Yes Yes 10 No Yes

6. Page Count Numeric No No 1 No No

7. Cover Image Image No No 1 No No

8. Published Date Numeric Yes Yes 1 No Yes

9. Publisher Text Yes Yes 1 No No

10. ISBN Numeric No No 1 No No

Classification Text/ No No 1 No No
11. Numeric

2. Field comparison

No. Desired Field Libib Field Notes

1. Author Authors In Libib, there is a field

with a similar name.

2. Title Title In Libib, there is a field

with a similar name.

3. Subject Tags In Libib, there is no field

that is comparable to
Subject. The database
record refers to the
subject as a tag.

4. Plot Description In Libib, the Plot field

can be refernced in the
Description field.
 Kolla / 002 / p. 14

5. Genre Tags In Libib, there is no field

that is comparable to
Genre. The database
record refers to the
Genre as a tag.

6. Page Count Pages In Libib, the Page Count

field can be refernced in
the Pages field.

7. Cover Image Cover Image In Libib, there is a field

with a similar name.

8. Published Date Published Date In Libib, there is a field

with a similar name.

9. Publisher Publisher In Libib, there is a field

with a similar name.

10. ISBN ISBN-13 In Libib, there is a field

with a similar name.

11. Classification Classification In Libib, there is a field

with a similar name.
 Kolla / 002 / p. 15

Appendix C. Record content and input rules

Field #: 1
Field Name: Authors
Semantics: Person who created the information object.
Chief Source of Information: Comic Book front cover.
Input Rules: Refer to Appendix F.
Example: Jerry Siegel

Field #: 2
Field Name: Title
Semantics: The word or an expression given to the information object.
Chief Source of Information: Comic Book front cover
Input Rules: The title should be typed exactly as it is. Each word in the title's name should have the first
letter capitalized. Don't forget to pay attention to articles, prepositions, and conjunctions. Ensure that the
same title that appears on the source of material is entered, as well as any unusual characters that might
appear.
Example: Stephen King's Dark Tower The Gunsinger Born Battle of Tull

Field #: 3
Field Name: Tags
(Subject):
Semantics: Main theme the information object is based on.
Chief Source of Information: Comic Book front cover
Input Rules: The first letter of the subject should be capitalized.  Between two subjects, a comma should
be accompanied by a single space.
Example: Brave, College, Superheroes

(Genre)
Semantics: The nature of a information object determines which class it belongs to.
Chief Source of Information: Back side of title page.
Input Rules: The first letter of the Genre should be capitalized. Use Comma and Space between different
subject entries.
Example: Drama, Horror, Mystery, Love, Romance

Field #: 4
Field Name: Description
Semantics: A short depiction of the story.
Chief Source of Information: 1. Book cover front 2. Title page
Input Rules: The portrayal ought to be in 150 words. Ensure it isn't surpassing the constraint of 150
words. Utilize capital letters any place it is vital particularly for things. Grammar ought to be utilized in
likely manner.
Example: Following Peter's death just after The Amazing Spiderman, Otto Octavius had injected his
consciousness onto Peter's body, ready to show himself the Superior-Spiderman by becoming a stronger
superhero and human than Parker is ever. When Octavius beats the Sinister Six and gains critical praise.
Parker's conscience, which also resides inside his mind, hidden under Octavius, is unknowingly holding
him apart. Peter demonstrates his inability to sway Octavius in even the tiniest of respects. Octavius
unintentionally shares Peter's true affection for Mary, kissing her lover in the act.

Field #: 5
Field Name: Pages
Semantics: The absolute size that establish the story.
Chief Source of Information: Comic Book back.
 Kolla / 002 / p. 16

Input Rules: Enter a value in numeric format in particular. Don't count any of the pages that aren't
numbered.
Example: 240

Field #: 6
Field Name: Cover Image
Semantics: The Pictorial representation of the object.
Chief Source of Information: Comic book front
Input Rules: Enter the comic book name in comicsclub.com. Download the appropriate image from the
website.
Example:

Field #: 7
Field Name: Published Date
Semantics: The date on which the information object is published.
Chief Source of Information: Comic Book Cover (Front and Back)
Input Rules: Enter the date in YY/MM/DD format.
Example: 2013/07/05

Field #: 8
Field Name: Publisher
Semantics: The business that makes the information object open to the general public.
Chief Source of Information: Comic Book Cover
Input Rules: Refer to Appendix F.
Example: Marvel

Field #: 9
Field #: ISBN
Semantics: An identifier that is supposed to be one-of-a-kind to identify information object.
Chief Source of Information: Back side of title page.
Input Rules: Enter the ISBN number exactly as it appears on the source, excluding any hyphens. It must
be a 13-digit number.
Example: 9780785121442.

Field #: 10
Field #: Classification
Semantics: A code that is supposed to be one-of-a-kind to identify information object physically.
Chief Source of Information: Find details in Appendix E.
Input Rules: Find details in Appendix E.
Example: Thr2015Fig458
 Kolla / 002 / p. 17

Appendix D. Sample thesaurus

Alien
UF Foreigner
RT Wanderer

Bravery
RT Warrior

Crime
RT Death

Compassion
RT Love

Death
UF Demise
RT Crime

Dark
USE Horror

Daydream
RT Fantasy

Demise
USE Death

Fantasy
RT Daydream
NT Fiction

Fiction
BT Fantasy

Foreigner
USE Alien

Horror
UF Dark

Killer
UF Terminator
BT Vampire

Love
RT Compassion
NT Romance

Magic
RT Occult

Occult
RT Magic
 Kolla / 002 / p. 18

Outsider
USE Alien

Protagonist
NT Warrior

Romance
BT Love

Sweet Sixteen
RT Teen

Teen
UF Young
RT Sweet Sixteen

Terminator
USE Killer

Vampire
NT Killer

Wanderer
RT Alien

Warrior
RT Bravery
BT Protagonist

Young
USE Teen

Key:

USE – Use
UF – Use For
BT – Broader Term
NT – Narrow Term
RT – Related Term
 Kolla / 002 / p. 19

Appendix E. Classification scheme

1. Scheme

No. Genre Published Date Title

1. Adventure - Adv Check the rule below Check the rule below

2. Comedy - COM

3. Drama - Dra

4. Horror - Hor

5. Mystery - Mys

6. Love - Lov

7. Romance - Rom
8. Thriller - Thr

9. Suspense - Sus

10. Fiction - Fic

2. Notation rules

Facet name: Genre

Chief source of information: Refer to Genre from the Tags (Genre) field.
Notation rules: Use the first three letters of the Genre with first letter capital. In the event that there
are several genres choose the first one in alphabetical order.

Facet name: Published Date

Chief source of information: Refer to Year from the Published Date field.
Notation rules: Pick the year format (YYYY) in MM/DD/YYYY for the notation and add it to the
Genre facet without any spaces.

Facet name: Title

Chief source of information: Refer to title in the Title field.
Notation rules: Use the first three letters of the Title eliminate conjunctions & prepositions like The,
A, An, In. Also make sure the first letter is capital. If the Title is a One or Two letter word, then use
those letters as title notation also if title is a number use the first two numbers of that title.

3. Rule for unique number

Add the last three digits of the ISBN number after the title facet with no spaces.

4. Example

Classification code: Thr2015Fig458

Primary Facet: Genre: Thriller (Thr)
Secondary Facet: Published Date: 02-15-2015 (2015)
Third facet: Title: Fight Club 2 Aschan Edition (Fig)
Unique identifier: 9781616559458 (458)
 Kolla / 002 / p. 20

Appendix F. Name authority file

1. Record content and input rules

Field#: 1
Field Name: AuthorizedName
Semantics: One version of a proper name (Person or Publishing Company) that can be used in the
database field.
Input Rules: Pick the Original name of the person and add his nicknames in VariantNames. If the person
has used any aliases or recently changed the name, add those names to Variant names as well.
Otherwise add his/her Personal name in the order of first name, last name. Ignore any middle names,
initials and Suffixes. Capitalize all the First letters of names used.
Example: Stephen King

Field#: 2
Field Name: VariantNames
Semantics: Alternatives to the authorized name (Person or Publishing Company) or variants of it.
Input Rules: Pick all the alternative names or aliases of the person. You can also add the complete full
name of the person of first name, last name format with middle name between first and last name. Also,
add variant names as they are discovered. If there is more than one entry separate by a comma.
Capitalize all the First letters of words used.
Example: Stephen Edward King, King, Stephen, Stephen king’s

Field#: 3
Field Name: SourcesUsed
Semantics: The formal source of an authorized name is referred to in this reference.
Input Rules: Refer the authorized name from source file. Here it is Comicsclub.com. Enter similar to what
it appears on the website. Capitalization and punctuation should match with the source file.
Example: ComicsClub

2. Sample records

AuthorizedName: Stephen King

VariantNames: Stephen Edward King, King, Stephen, Stephen king’s
SourcesUsed: ComicsClub

AuthorizedName: Brian Bendis

VariantNames: Brian Michael Bendis, Brian, Michael, Bendis
SourcesUsed: ComicsClub

AuthorizedName: Scott Snyder

VariantNames: Scott, Snyder, Scot Snyder, Scott Snider
SourcesUsed: ComicsClub

AuthorizedName: Chuck Palahniuk

VariantNames: Charles Michael Palahniuk, Palahniuk, Charles, Chuck, Michael, Charles Palahniuk
SourcesUsed: ComicsClub

AuthorizedName: Catana Chetwynd

VariantNames: Catana, Chetwynd, Katana, Katana Chetwynd, Katana Chetwind
SourcesUsed: ComicsClub

AuthorizedName: Dan Slott

VariantNames: Dan Slot, Dan, Slott, Slot
SourcesUsed: ComicsClub
AuthorizedName: Dark Horse
 Kolla / 002 / p. 21

VariantNames: Dark Horse Comics, Horse, Dark House

SourcesUsed: ComicsClub

AuthorizedName: Tom Waltz

VariantNames: Tom, Tom Walz, Waltz, Walz
SourcesUsed: ComicsClub

AuthorizedName: Marvel
VariantNames: Marvel Comics, Marvel House,
SourcesUsed: ComicsClub

AuthorizedName: Brahm Revel

VariantNames: Brahm, Revel, Brahm Reval, Reval
SourcesUsed: ComicsClub

Appendix G. Sample records

Database Record-1
 Kolla / 002 / p. 22

Database Record-2

Database Record-3

Database Record-4
 Kolla / 002 / p. 23

Database Record-5

Database Record-6

Database Record-7
 Kolla / 002 / p. 24

Database Record-8

Database Record-9

Database Record-10
Kolla / 002 / p. 25