Archive

Syntax for writing the link

If you put a URL into the body of a node, one of Drupal's input filters will automatically turn that URL into a clickable web link, like this: http://www.youtube.com/watch?v=Fc9B2g_1h1o

You can also use a special "markdown" shortcut for making links; this is better for referring to other pages on CNMAT's Drupal site.

Change your website notification preferences by going to "My Account" on the left, then click edit and scroll down to "Email Notifications". Here you can change your preferences to not receive any email notifications, or manage them on a case by case basis.

The website can e-mail you when new content is added or a comment is made to a page.

This feature can be enabled from most pages by clicking the link at the bottom of the page, "Subscribe post", or at content-creation type by checking "Subscribe" under the "Subscriptions" tab.

---

**Common Use Case:**

- Creating a special folder for Case Tracker notices

**General Instructions:**

#Overview

- An unpublished node is not viewable to anyone but the author of that node.

- Users can utilize this feature to save nodes of any type as a draft.

#Saving your post as a draft

- If the post is still a draft, uncheck the box next to "Published" under the "Publishing Options" drop-down at the bottom of the page.

[http://cnmat.berkeley.edu/library/cnmat_users_manual/research_handbook/s...| Preparing videos for documentation]

[http://cnmat.berkeley.edu/user/adrian_freed/blog/2008/12/23/budgeting_vi...| Budgeting for video transfer]

Roles grant functional capabilities to a user, and must be managed by the user administrator.
The permissions granted to a user are the sum of all assigned roles. The authenticated user role is automatic for anyone with a user account and logged in. The anonymous user role is automatic for any visitor without an account or not logged in.

**Current List of Roles:**

anonymous user:

These are how-tos and references for ongoing website development.

#Overview

The Engaging Music Panel contains links to the automatically generated MIC resource page. The terms are arranged hierarchically in four major categories. These categories appear on the left side panel, and once clicked, that category's terms appear on the right.

#Overview

Only users with certain access privileges are able to edit the taxonomy. Be sure to think carefully about if the new term is really necessary. The website taxonomy is already large, and too many terms can lead to misclassification and confusion.

The complete website taxonomy is located here.

#Considerations

#Overview
The names that appear in the left hand column are updated manually. To generate a page of all of the Music and Inter Arts Projects associated with a person simply enter the Term ID of that person's name after the URL "http://cnmat.berkeley.edu/new_music/people/[TID Here]"

#Note
Only Website Administrators have the privileges necessary to add a name to the New Music Panel.

To change the person listed as the manager of a group, simply edit the group node, then scroll down to the drop-down titled "Authoring Information". Whatever name is in the "Group Manager" field will appear as the manager.

There are three related use cases for archiving work done at CNMAT:

1. An “exit interview”, where somebody leaving CNMAT makes a record of the work (s)he did here

2. A “project wrap-up”, where we preserve the accomplishments of a project that is now over (e.g., a concert that happened yesterday)

3. Ongoing incremental archiving (e.g., maintenance of our Max/MSP externals)

"Ferris" is a CNMAT researcher with programming skills. He works on multiple simultaneous projects on various machines at home and at CNMAT, as well as supporting older software written by other people. He has working copies of all his software on all of his machines, which he backs up and keeps synchronized entirely through CNMAT’s version control repository.

The exploration stage involves a search within the CNMAT information infrastructure and external sources for possible dates, performers, venues, and technical resources.

“Joan” is a graduate student composer in the UC Berkeley music department, interested in learning more about computer music, so a faculty member points her to the website and recommends she look around and see what interests her.

"Joe" is interested in additive synthesis and he navigates to our Drupal-based web content management platform that organizes a page of all “additive synthesis” work at CNMAT. “Joe” might see the following:

* Scores, software, and audio and video recordings of music composed and/or performed at CNMAT that used additive synthesis.

Suppose a microphone is accidentally broken at a concert. This should be reported in such a way that someone will be notiified, the gear will be marked as not available for reservations, and then when it's fixed that will be noted, the history of the maintenance will be saved, etc.

exploratory phase: identify the software component and learn its development history.

- svn update
- svn log -v _filename_
- (if necessary) svn diff -r 123:1000 _filename_

Coordination phase:

checking out the latest source code and any required development tools from inventory.

- svn update
- svn checkout _package\_name_

As an example, the node for the piece _Corail_ should have tags indicating all of the following:

+ it is a musical composition
+ it was written by Edmund Campion
+ it was composed in 2000-2001
+ it was composed at CNMAT
+ it is for saxophone
+ it is an interactive real-time piece
+ it uses Max/MSP
+ it uses pitch detection
+ it uses sample playback synthesis
+ it uses live sampling