|
|
| Line 1: |
Line 1: |
| <div style="width:98%; border:3px solid #0063bf; overflow:hidden; background-color: #FFFFFF; padding:16px 16px 16px 16px">
| | Welcome! |
| <div style="text-align:left; font-size:1.5em; color: #0063bf">Welcome to Wikibase Cloud!</div>
| |
| <div style="text-align:left;">This is your main page. For the start we have assembled some information for you that we think might be useful. This page is supposed to work for you. Feel free to change it to whatever you would like it to be. You can always copy its content to another place or just remove it entirely whenever you're ready. <br>
| |
| ''We'd also be happy to hear if this page was helpful for you and/or what we could improve via [https://www.wikibase.cloud/contact our contact form]. Thanks!''</div>
| |
| </div>
| |
| __NOTOC__
| |
| = Where to start =
| |
| [https://www.mediawiki.org/wiki/Wikibase/Wikibase.cloud/First_steps Have a look at some possible first steps] you could take after creating your new wikibase.
| |
|
| |
|
| ==What do i need to know about how Wikibase works?== | | == Aim & Scope == |
| ===Wikibase ecosystem===
| |
| There are many Wikibases in the ecosystem. The community around Wikibase includes Wikibase users, partners, volunteer developers and tool builders, forming the vibrant and diverse Wikibase Ecosystem. In this ecosystem, we imagine that one day all the Wikibase instances will be connected between themselves and back to Wikidata.
| |
| ===How is information structured?===
| |
| Data is stored in Wikibase in the shape of Items. Each item is accorded its own page. Items are used to represent all the things in human knowledge, including topics, concepts, and objects. For example, the "1988 Summer Olympics", "love", "Elvis Presley", and "gorilla" can all be items.
| |
| Items are made up of Statements that describe detailed characteristics of an Item. A statement (graph format: Subject-Predicate-Object) is how the information we know about an item - the data we have about it - gets recorded in your Wikibase instance.
| |
| This happens by pairing a property with at least one value; this pair is at the heart of a statement. Statements also serve to connect items to each other, resulting in a linked data structure.
| |
|
| |
|
| [https://upload.wikimedia.org/wikipedia/commons/6/60/Linked_Data_-_San_Francisco.svg Check out this visualization of the linked data structure]
| | The world of contemporary music is constantly changing and evolving, and our research and identification tools need to keep up. We are currently unprecedented developments in every facet of music; should the same not be seen in discoverability and knowledge sharing? |
|
| |
|
| The property in a statement describes the data value, and can be thought of as a category of data like "color", "population," or "Commons media" (files hosted on Wikimedia Commons). The value in the statement is the actual piece of data that describes the item. Each property has a [https://www.wikidata.org/wiki/Special:MyLanguage/Help:Data_type data type] which defines the kind of values allowed in statements with that property. For example, the property “date of birth” will only accept data in the format of a date. | | The Computer Music Preservation and Electronic Library (COMPEL) seeks to meet the needs of modern musicians in three ways: by providing visibility to their work, by supporting the exchange of ideas by a robust network of connections between people and ideas, and by preserving works in their original forms for future use and study. |
|
| |
|
| [https://upload.wikimedia.org/wikipedia/commons/a/ae/Datamodel_in_Wikidata.svg Check out this visualisation of the structure of an item]
| | The first step is visibility. COMPEL is building a database of computer music and the artists who work with it, including composers, performers, technologists, musicologists, and anyone else who participates in the creation of sound-based digital art. We collect data that pertains to people, their artistic works, and discrete performances- check out one of our [[Item:Q56|sample]] [[Item:Q19|records]] for a better idea of what that entails! |
|
| |
|
| '''Example'''
| | The next step is exchange. Rather than a static list of compositions, COMPEL aims to display the connections between composers and their inspirations, between performers and the compositions they play, the ongoing discussions about music, and everything in between. In short, COMPEL is a relational database, not just a list of people and pieces. Eventually, this will mean that researchers will be able to ask and answer complicated questions, like "how many composers working with electronics are employed at universities?" or "what instruments are most commonly used in electroacoustic pieces?" |
| In order to record information about the occupation of Marie Curie, you would need to add a statement to the item for [https://www.wikidata.org/wiki/Q7186 Marie Curie (Q7186)]. Using the property, [https://www.wikidata.org/wiki/Property:P106 occupation (P106)], you could then add the value [https://www.wikidata.org/wiki/Q169470 physicist (Q169470)]. You could also add the value [https://www.wikidata.org/wiki/Q593644 chemist (Q593644)]. Note how both chemist and physicist are each their own item, thereby allowing Marie Curie to be linked to these items.
| |
|
| |
|
| == How to create items + properties + (what is a good property) ==
| | The final step is preservation. Concert music that includes electronics is complicated to create and includes the utilization of many software and hardware components. While digital preservation is a rapidly growing field, there are no standards or "best practices" yet developed for musical objects in their original form- not recordings of performances, but the electronics themselves. COMPEL aims to develop a preservation strategy for electronic music and multimedia objects to ensure that the works created now are available for future performance and study. |
| Create a new Item with [[Special:NewItem]] on the menu to the left. You will be taken to a page that asks you to give the new item a [https://www.wikidata.org/wiki/Wikidata:Glossary#Label label] and a [https://www.wikidata.org/wiki/Wikidata:Glossary#Description description]. When you're done, click "Create".
| |
|
| |
|
| Create the property with [[Special:NewProperty]].
| | == FAQ == |
| Property entities can be edited like [https://www.wikidata.org/wiki/Special:MyLanguage/Help:Item item entities] with labels, descriptions, [https://www.wikidata.org/wiki/Special:MyLanguage/Help:Aliases aliases], and statements.
| |
| '''Property labels''' should be as unambiguous as possible so that it is clear to a user which property is the correct one to use when editing items and adding statements. Properties rarely refer to commonly known concepts but they are more constructs of the Wikidata with specific meanings. Unlike items, property labels must be unique.
| |
| '''Property descriptions''' are less relevant for disambiguation but they should provide enough information about the scope and context of the property so that users understand appropriate usage of the property without having to consult additional help.
| |
| '''Property aliases''' should include all alternative ways of referring to the property.
| |
|
| |
|
| '''Example:''' | | '''Is COMPEL an archive?''' |
| property: [https://www.wikidata.org/wiki/Property:P161 P161]
| |
| label: cast member
| |
| description: actor performing live for a camera or audience
| |
| aliases: film starring; actor; actress; starring
| |
|
| |
|
| To create and delete data using tools, [https://www.mediawiki.org/wiki/Wikibase/Creating%20and%20deleting%20data have a look at this list in the documentation].
| | Not yet! Right now, we're collecting data to create a network of linked data about the music community. This includes composers, performers, instrument and software creators, researchers, ensembles, and anyone else involved with making music. ''We do not hold individual objects, electronic or otherwise, at this time!''When we integrate preservation, we'll announce it, likely with great enthusiasm and ceremony. |
|
| |
|
| Another way is via the [https://www.mediawiki.org/wiki/Wikibase/API Wikibase API] that allows querying, adding, removing and editing information on Wikidata or any other Wikibase instance. A new version of the API is in the works with the [https://doc.wikimedia.org/Wikibase/master/php/repo%20rest-api%20README.html REST API].
| | '''What information do you collect?''' |
|
| |
|
| == Don’t panic -> links to help ==
| | Anything you're willing to share! This can include metadata (for example, a composer's name, the number of performers needed for a piece, the size of an installation, or the members of an ensemble) or in some cases, digital objects (generally, just photos). We prefer that scores and recordings be made available on the musician's own site; we will provide a link out to that. This allows musicians to track their own use metrics. |
| This is a lot of information and possibilities and might seem daunting. Don’t panic. There’s a lot of [https://www.mediawiki.org/wiki/Wikibase/Wikibase.cloud documentation] for you to read, [https://www.wikibase.cloud/discovery many other Wikibases you can look at] to get inspired, a [https://t.me/joinchat/FgqAnxNQYOeAKmyZTIId9g community] that is happy to help out with any questions, and [https://www.wikibase.cloud/contact the development team] who’s happy to support you where needed. | |
|
| |
|
| == Last but not least == | | '''What is linked data, and why do you keep mentioning it?''' |
| To edit this page, make sure you are logged in and click on -edit- on the top right of this page to change or remove the content.
| | |
| | Most of us are familiar with hyperlinks, which we see everywhere online, including this page. Linked data utilizes a similar concept, but rather than just link pages together, it links ideas in a web of connections. Each idea is editable in itself, which updates any changes across the database. This type of data allows for much more robust searching and visualizations. Linked data can be read by humans and machines alike. |
| | |
| | '''Something is incorrect in my record. How do I fix it?''' |
| | |
| | At the moment, the most efficient way to correct a record is to email compelmusic@vt.edu with a description of the needed change. Please include a link to the page in question. |
| | |
| | == Glossary == |
| | |
| | There are a lot of terms to describe music, especially electronic music. Many are similar, but not identical. COMPEL strikes a balance between nuanced, granular data, and data with broad enough terms to be useful. Here, we include our vocabulary as we define our terms, including "aliases-" terms that we understand have individual nuances, but we choose one to represent all of them. |
| | |
| | == Collaborators == |
| | |
| | COMPEL is hosted by Virginia Tech, but exists thanks to the diligent work of our collaborators: |
| | |
| | Kristopher Bendrick, Western Michigan University, University of Pennsylvania |
| | |
| | Carolyn Borcherding, Baldwin Wallace University |
| | |
| | Ico Bukvic, Virginia Tech |
| | |
| | Gabrielle Cerberville, University of Virginia |
| | |
| | Michael Flynn, freelance composer |
| | |
| | Kara Long, Virginia Tech |
| | |
| | Raul Masu |
| | |
| | Andi Ogier, Virginia Tech |
| | |
| | James Tuttle, Virginia Tech |
| | |
| | Hollis Wittman, Virginia Tech |