Purpose
To experience developing an organized system from scratch. To experience working with a group to develop a full organizing system including the use of taxonomies and/or controlled vocabularies as well as encoding of metadata.
Description
You will need to work with a group for this project. Please identify two to three individuals with whom you can work on this project. You will need to share your collaborative document with me.
Develop an organizing system to organize material on a website for a resource collection of your choice. Here are a few resource schemas you may consider using:
- Recipe [https://schema.org/RecipeLinks to an external site.
]
- Music Recording [https://schema.org/MusicRecordingLinks to an external site.
]
- Drug [https://schema.org/DrugLinks to an external site.
]
- Video Game [https://schema.org/VideoGameLinks to an external site.
]
- Vehicle [https://schema.org/VehicleLinks to an external site.
]
- Dublin Core (General Purpose) [https://www.dublincore.org/specifications/dublin-core/dcmi-terms/Links to an external site.
]
Alternatively, you may choose your own topic and use the Dublin Core Schema and Omeka to set up your organized system. Your organizing system should include the selection of appropriate elements from the schema, the development of a basic taxonomy, and the selection or development of appropriate controlled vocabularies for names of persons and organizations (even when not specifically required in the schema), as well as appropriate controlled vocabulary formatting, for dates, languages and identifiers where required or recommended by the schema.
Your completed project should include:
- a front page listing the members of the group
- a discussion of the design decisions you must make for this system to be efficient and effective.
You will develop a demo to show how your system would work in practice. While your demonstration does not need to be a fully working website or model, you should include a working faceted taxonomy and metadata encodings corresponding to at least three (3) of your created metadata records. You may use paper mockups or slides to demonstrate how the system would work.
You may use an existing digital library tool such as Omeka, code a demo yourself in HTML, use a website builder, or create a slide presentation/video showing how your system would work.
Your project must include the following:
1) a page discussing design decisions [This should include answering the questions posed herehttps://berkeley.pressbooks.pub/tdo4p/chapter/design-decisions-in-organizing-systems-introduction/Links to an external site.
]
2) a minimum of 10 metadata records for your selected resources formatted according to the example shown in the table below (your metadata record should use a minimum of 8 elements/properties) [skill learned in Assignment 3]:
Metadata Element
|
Value
|
Content/Vocabulary Standard for Formatting
|
dc.title
|
The Discipline of Organizing: 4thProfessional Edition
|
|
dc.creator
|
Glushko, Robert J.
|
LCNAF
|
dc.subject
|
Information organization.
|
LCSH
|
dc.description
|
This textbook takes a multi-disciplinary approach to the field of information organization.
|
|
dc.publisher
|
Glushko, Robert J.
|
|
dc.contributor
|
|
|
dc.date
|
XXXXXXXXXX
|
W3CDTF
|
dc.type
|
Text
|
DCMI-Type
|
dc.format
|
application/pdf
|
IMT
|
dc.identifier
|
XXXXXXXXXX
|
|
dc.source
|
https://berkeley.pressbooks.pub/tdo4p/
|
|
dc.language
|
en
|
ISO 639-2
|
NB. Since you will be using schema.org your property/element names will not be the same as shown in the table, since that uses Dublin Core
3) validated metadata encoding in rdf/xml or json for three (3) of your metadata records [See Week 11 Module]
4) the identification and use of established controlled vocabularies for names of persons and organizations (Seehttps://en.wikipedia.org/wiki/Authority_controlLinks to an external site.
) and for all elements where a content standard is recommended or required for a property by the schema eg. language, date. [See Week 5 module]
5) the set of interactions you will enable on your site (these can be built into the system or you can demonstrate how you would like it to work) [Seehttps://berkeley.pressbooks.pub/tdo4p/chapter/designing-resource-based-interactions/Links to an external site.
],
5) a hierarchical taxonomy that will support organization of your resources and at least three facets to enable filtering of the search results. [skill learned in Assignment 4 and Week 10 module]
6) demo/overview of how your website would look with enabled taxonomy and results displayed
NOTE:
It is recommended that you work with at least one other person on this project. Because it is very important to experience issues involving lack of consensus for taxonomy or controlled vocabulary development during this project. A student who would prefer to work alone must reach out to me for agreement first and must also write an additional short paper which will compare their system to a similar system for a similar experience.
Submission Components:
- Submit a single pdf document or presentation which combines these elements of your organized system. You may present the document as slides (with or without voice) as you desire.Do not use Prezi or any similar tool.
one page discussing design decisions
10 metadata records
3 validated encoded metadata records (rdf/xml, json)
mock ups of interactions showing how they are enabled
full faceted taxonomy that organizes resources and supports search and browse
demo/overview of how your website would look with enabled taxonomy and results displayed
final page providing summary of the work done, decisions made, challenges, disagreements and resolutions, and any final thoughts. (Include a link to your collaborative document on this final page, be sure permissions are set appropriately for me to view this document)
- Students who are working alone should add an additional document, 400 words, comparing their system to an existing system on a similar topic/with a similar function. If you work in a group, you will have the chance to discuss issues of compromise and consensus that a solo project will miss. Comparing your system to an existing system will still allow you to experience and discuss some of these issues.
Group Sign Up
Group membership is a self enroll, you will not be randomly assigned. Do the following:
- Please identify the Final Project Group Sets and self-sign up with one of the available groups. Instructions for self-sign up may be foundat this linkLinks to an external site.
. (If you choose to work alone, please contact me for permission and so that I might set up Canvas to accept your work.)
- Create a collaborative document (Microsoft Word or Google Docs) in which you will all be working and share that file with me.
- Please use one page of the collaborative document to outline tasks and how you will be dividing those tasks between group members.
- Please add a notation if a group member fails to complete their assigned and agreed on tasks.