Go directly to :

• The tags
• Languages
• Body and Input formats
• File Attachments
• Perceptive Tests
• URL Aliases
• Menu Settings
  
• Differents types of contents
  • A note on General and Flexible Media
  • Audio
  • Blog entry
  • General Media
  • Flexible Media
  • News
  • Project Form
  • Publication
  • Researcher Profile
  • Researcher Profile Page
  • Software Form
• Info +

The tags

Whatever the content type, you can tag it thanks to the Vocabularies section of the creating form. Each vocabulary relates to an aspect of the content type you are creating. Each vocabulary is composed of a number of terms, ways of describing that particular aspect. The terms are what the content will be "tagged" with. To select some terms for a particular vocabulary, click on the vocabulary's drop down list title to view them. The available terms are displayed as check boxes. Checking a term's box will at that tag to the content once you save the form. It is possible to tag content with multiple terms from one vocabulary by checking multiple boxes. For some vocabularies you will be able to create new terms. For example the "Software Projects" vocabulary allows you create new terms for any new software forms you may be creating. If a suitable term is not already available, simply type the desired name of the term in the field. the term will then be created and tagged to the form when you hit save, it will also be available as a checkbox from then on. The People Associated vocabulary: This is a unique vocabulary. There terms of this vocabulary are made up of all the names of the Analyse-Synthèse team members. Every content created should be tagged with the names of the people who are involved in the project/software/profile/demonstration the content refers to. This may just be one name, in the case of a researcher profile or a personal demonstration or it may be many names in the case of a software form. The unique thing about this vocabulary is that your name is automatically tagged to any piece of content that you create, making the process of creating content a little easier and quicker. This is based on your "Personal tag" setting on your account page. You can see the tag that has been added for you in the "Auto Tag" section of the form. The site assumes that you will have been involved in a piece of content that you are creating. You can then go to the "Personnes Associé" vocabulary and tag and other relevant names. If you want to create content, but not be tagged to it, simply delete your name from the Auto Tag section and leave it blank.

Languages

The default language is: Language neutral. Choosing a language for your content makes it invisible for the other languages. Once the content has been created in one language you can translate it into the other one using the translate tab. Don't forget to translate the menu link title (c.f. paragraph above). If you cannot create a translation of the piece of content you are adding it would be better to leave the language selection at language neutral. Language neutral items will still populate all relevant lists on the site in both the French and English sides of the site and language neutral menu links will be available in the relevant places. For example if you create a language neutral software form, the menu link that you create for it will be available in both "software" on the English side of the site and "logiciel" on the French side

Body and Input formats

To fill in the Body of the user is provided with a number of options which are displayed in the "Input format" section of a node edit form. The best choice for most users is "Page input", which is the default option so that in most cases it is not necessary to directly choose an input format.

The "Page input" option allows the user to user the TinyMCE Rich-Text editor to create the body of their content. TinyMCE is a WYSIWYG (What You See Is What You Get) editor which will be instantly familiar to an Microsoft Word user. The editor allows the user to easily (without editing html) create rich pages and also to insert Latex. LaTex exemple:

The "Disable rich-text" link to the bottom of the editor allows a user to enter simple text, HTML or Latex in a simple text field. This is especially useful for very simple pages.

The TinyMCE interface provides a number of buttons, most of which carry out typical functions in the typical way (such as creating bold text, cutting and pasting, undoing an action etc).

NOTE: It is possible to use TinyMCE to insert tables (using the table button) which can be a nice way to present information (particularly with audio files and descriptions). The tables interface also provides some options for styling the table. The site's main CSS file however can override some options presented there and one important case is when creating tables with no borders (tables just used for layout purposes). In order to remove the borders from your table the best way is to highlight all the cells within the table by clicking and dragging the mouse, selecting the "Table cell properties" button. Going to the "advanced" section and typing "noborders" into the "id" field.

Some extra buttons of interest here include the "Paste from Word" button, which appear as a clip board with the Word logo attached to it. This allows text created in word to be pasted into the editor whilst retaining the formatting applied to it. The "Toggle fullscreen mode" button to the left of it is very useful when editing large amounts of text.

A very useful button is the HTML editor which is simply labelled "HTML". The button loads a window which allows users to directly edit the html behind the rich text. The main use of this feature being to add <anasynref> tags to the code in order to reference team publications. Each article in the Scientific Articles section can be referenced within a body of text. To do this simply enter the following in the desired location within the html code:

<anasynref>Cote Médiathèque</anasynref>

Where "Cote Médiathèque" is the unique identifier for the desired report. For example "Yeh10a". This will produce a reference of the report which links to the report's overview on articles.ircam.fr. For the above example: (C. Yeh, A. Roebel, X. Rodet, 2010a). One can also directly embed a complete reference for an article, specified with its cote médiathèque, by including the [INLINE] symbol:

<anasynref>[INLINE]Yeh10a</anasynref>

Author does not exist

It is also possible to use the <anasynref> tags to create links to a view of all the references in the Scientific Articles section and also to apply various filtering options. Access to the references is achieved through the use of the symbol [ALL]:

<anasynref>[ALL]</anasynref> Analysis/Synthesis' Publications

provides a link to the All view of the Scientific Articles section. Using this as a starting point it is possible to apply a filter for a particular author:

<anasynref>[ALL]X. Rodet</anasynref> X. Rodet's Publications

for example gives a link to all articles by X. Rodet. It is important to write the author name exactly as it is written in the report itself. The same results can be displayed in an embedded fashion, this is especially useful for profile pages;

<anasynref>[EMBED]X. Rodet</anasynref> X. Rodet's Publications - (clear)X. Rodet's Publications - (clear)

Using the [EMBED] identifier produces two links. The main link when clicked will produce the results of the search in a drop-down fashion. The second link allows the user to clear the results and return to normal screen size. An author's articles can also be displayed inline by using the [INLINE] symbol instead:

<anasynref>[INLINE]M. Avanzi</anasynref>

Author does not exist

With this method it is also possible to perform some filtering on the results via the use of three extra symbols. A request for only specific types of articles to be returned using the [type] symbol.

<anasynref>[INLINE]M. Avanzi[type]colloques</anasynref>

Author does not exist

The types are defined in French for convenience. A list of allowed types is given below. The members of the list are the exact text string that must be used for that type, they can therefore be copied directly into the html of a reference:

revuesacomite
revuessancomite
livres
colloques
memoires
rapports
monographies
revuesspeciaux

Below is the English equivalent of these strings. Note that only the above French strings can be used in a reference:

Refereed journals articles
Non-refereed journals articles
Book sections
Proceedings
Dissertations
Reports
Edited books
Journal special issues 

The [year] symbol allows the user to either specify a single year to filter by or to specify a period of time by using negative numbers to provide a "years ago" value.

<anasynref>[INLINE]M. Avanzi[year]2009</anasynref> for example will return all articles from 2009, as below:

Author does not exist

<anasynref>[INLINE]M. Avanzi[year]-1</anasynref> will return all results published from at least one year ago (inclusive) as below:

Author does not exist

The above approach can be used to produce a list of "recent" articles. Finally, the [notitle] symbol removes the year group titles from whatever results are returned by rest of the tag:

<anasynref>[INLINE]M. Avanzi[notitle]</anasynref>

Author does not exist

Of course, it is possible to use the three symbols together in any combination so long as the position of the symbols is always [notitle] > [year] > [type], ie for any combination [type] must always be first and [notitle] must always be last.

Returning to the [ALL] function, it is also possible to filter by year using the symbol [year] followed by a year:

<anasynref>[ALL][year]2009</anasynref> Analysis/Synthesis' Publications, 2009

will show all articles produced by the team in 2009. The author and year filters can be combined like so:

<anasynref>[ALL]X. Rodet[year]2010</anasynref> X. Rodet's Publications, 2009

will show all articles produced by X. Rodet in the year 2009. When filtering for an author it is possible to filter for multiple authors using the AND:

<anasynref>[ALL]X. Rodet AND A. Roebel</anasynref> Collaborative Publications by X. Rodet and A. Roebel

and OR:

<anasynref>[ALL]X. Rodet OR A. Roebel</anasynref> X. Rodet and A. Roebel's Publications

keywords. The examples will show all articles who's authors include BOTH X. Rodet AND A. Roebel and include EITHER X. Rodet OR A. Roebel respectively. Of course, it is possible to use these conditions whilst also filtering by year:

<anasynref>[ALL]X. Rodet AND A. Roebel[year]2009</anasynref> Collaborative Publications by X. Rodet and A. Roebel, 2009

producing a list of all the articles written by BOTH X. Rodet AND A. Roebel in the year 2009.

As well as the anasynref tags there are also two other tags useful when working with references. The <externalref> tag allows individual articles produced outside of the Analyse/Synthèse team to be embedded inline on a page in the same format as shown above. The details of the article are specified using various placeholders. The simplest form is as follows:

<externalref>[authors] ... [title] ... [context] ... [year] ... </externalref>

Here, [context] indicates the purpose for which the article was written. For example: the name and details of the journal it was presented in, the name and host institution of a conference, the name, chapter and page details of a book etc. This form of externalref is the minimum amount of detail required for a complete, working reference, ie [authors], [title], [context] and [year] must be included for a correct reference. Below is a working example using this form:

<externalref>[authors]M. Marshall, M Wanderley[title]Vibrotactile Feedback in Digital Musical Instruments[context]Proceedings of the 2006 International Conference on New Interfaces for Musical Expression (NIME06), Paris, France[year]2006</externalref>

• M. Marshall, M Wanderley « Vibrotactile Feedback in Digital Musical Instruments », Proceedings of the 2006 International Conference on New Interfaces for Musical Expression (NIME06), Paris, France, 2006, Google Scholar

Two extra items of information can be added. Using the [web] symbol, it is possible to provide the address of an online version of the report which will be displayed as a link in the title given:

<externalref>[authors]M. Marshall, M Wanderley[title]Vibrotactile Feedback in Digital Musical Instruments[context]Proceedings of the 2006 International Conference on New Interfaces for Musical Expression (NIME06), Paris, France[year]2006[web]http://nime.org/2006/proc/nime2006_226.pdf</externalref>

• M. Marshall, M Wanderley « Vibrotactile Feedback in Digital Musical Instruments », Proceedings of the 2006 International Conference on New Interfaces for Musical Expression (NIME06), Paris, France, 2006, Google Scholar

The [details] symbol can be used to provide the address of a website containing additional information on the report (such as a synopsis, publishing details, PhD thesis information etc):

<externalref>[authors]M. Marshall, M Wanderley[title]Vibrotactile Feedback in Digital Musical Instruments[context]Proceedings of the 2006 International Conference on New Interfaces for Musical Expression (NIME06), Paris, France[year]2006[details]http://portal.acm.org/citation.cfm?id=1142215.1142272</externalref>

• M. Marshall, M Wanderley « Vibrotactile Feedback in Digital Musical Instruments », Proceedings of the 2006 International Conference on New Interfaces for Musical Expression (NIME06), Paris, France, 2006, details - Google Scholar

Of course, both of the above symbols can be used together with the others to form a fully detailed reference:

<externalref>[authors]M. Marshall, M Wanderley[title]Vibrotactile Feedback in Digital Musical Instruments[context]Proceedings of the 2006 International Conference on New Interfaces for Musical Expression (NIME06), Paris, France[year]2006[web]http://nime.org/2006/proc/nime2006_226.pdf
[details]http://portal.acm.org/citation.cfm?id=1142215.1142272</externalref>

• M. Marshall, M Wanderley « Vibrotactile Feedback in Digital Musical Instruments », Proceedings of the 2006 International Conference on New Interfaces for Musical Expression (NIME06), Paris, France, 2006, details - Google Scholar

It is important to note the the order of the various symbols presented above must be correct for the reference to be produced. That is, the symbols must be in the order [authors][title][context][year] ( [web][details] ) for the externalref tag to be valid. All of the formatting displayed in the above examples (italicized font, links etc) is automatic.

Finally, the <reftitle> tag can be used simply to create customized titles in the same style as those seen above in order to group together any external references or inline references to an individual anasynth article:

<reftitle>My Title</reftitle>

All of the above tags allow the user to space the arguments with line breaks to make the HTML more readable. For example:

<anasynref>
[INLINE] M. Avanzi
[type] colloques
[year] -1
[notitle]
</anasynref>

It is possible to separate each section of the tag with a single line break. Multiple line breaks between sections will break the tag and result in an error.

For a very concise reference version of the above information, see here. Remark: If you are using HTML, it is not necessary to put all the common basic tags (<html>, <head>, <body>, ...). Just put the tags you need (<ul>, <p>, <B>, ...). For more informations:

HTML Guide All LaTex Symbols Compose tips

File Attachments

Using the TinyMCE editor there are a number of choices when it comes to uploading files. Each choice will involve the use of the IMCE file browser if a specific file url is not specified. The browser can be accessed by clicking the "browse" button next to the url field of any of the upload option's control windows; which will be described shortly. Each user has a personal directory automatically created for them on the server, which is labelled after their user name. When the browser window loads it will open in that user's personal directory. The main controls for the browser are the tabs along the top of the window. The region to the left shows the directory tree and the region to the right shows the contents of the current directory. The region to the bottom left is a log used to display messages regarding uploads, editing functions, errors etc and the bottom right region provides previews of images.

Users can create any number and any depth of subdirectories from their personal directory by going to the "Manage directories" tab. This presents a simple field allowing the user to choose a name for and add a subdirectory to the current directory (selected by clicking on a directory in the tree to the left). The Manage directories section also allows users to delete subdirectories by selecting one and then clicking the "Remove" button.

The "Upload" tab allows users to upload a file into the current directory. "Choose file" will bring up a browser into the users computer and upload will upload the chosen file to the server. In order to create the reference to the file in the TinyMCE editor it is necessary to select the desired file and click the "Send to tinymce" tab. This will return the user to the main options window of the upload style selected.

The "Delete" allows a file to be removed from the server simply by selecting the file and clicking the delete tab.

There are also some image editing operations which can be performed by selecting an image and clicking the relevant tab, which will provide some options for the transformation. The operations are creating thumbnails, resizing and cropping.

The file browser as well as the above features are also accessible from a user's "my account" section by going to My account->File Browser. From here user's can upload files and manage directories in their personal directory without having to go to some content and insert a link / image etc, instead uploading files to perhaps be referenced later. 

Insert / embed media: This button looks like a two frames of a roll of film. This feature allows audio, video and flash to be embedded into the page so the media can be played on the page being created. The type field allows the user to select a relevant player type for the media being uploaded. The File/URL field allows the user to specify the file and also provides a browser button for uploads. There is also a field to specify the size of the player. The advanced section offers some options such as "auto play". Videos from the web (ie YouTube) can be embedded by selecting the "flash" type and pasting the url (not the embed code) of the video. Audio and video files can be uploaded and embedded by selecting the "quicktime" type. For audio files it may be desirable to reduce the size of the player some what. A 200 x 20 player makes for a good looking audio embed.

Insert / edit image: This button looks like a cartoon picture of a tree and provides much the same functions as above but is aimed specifically towards embedding images. Images can be cropped and resized in the browser window by using the relevant tabs.

Insert / edit link: This button looks like a metal chain link. This feature provides similar upload features to those mentioned above but instead of embedding media it simply creates a link to that file on the server. This is therefore the obvious choice for uploading and including non-video/audio/image files such as pdf and html.

Dew Player: This is an mp3 player plugin which allows mp3 files to be embedded into a page with an attractive, light-weight flash interface providing some simple controls. There are two main ways of inserting a dew player with TinyMCE.

The first way (and arguably the most tedious) is to use the Insert / embed media button described above. Use the browser button to upload/select your file and send it to TinyMCE. Next, at the beginning of that file path (in the file/URL field) insert this text - /drupal6/sites/all/plugins/dewplayer.swf?mp3= - without editing the file path inserted previously. This will then create a flash placeholder in the editor which when the page is saved and viewed will become the dew player. From the Insert / embed media window it is also possible to choose some "advanced" settings, one of the most useful of which is "wmode" (background setting) which is set to "transparent" when using the next method of insertion.

The second (and possibly easiest) way is to use the <dewplayer> tag. The tag must be added in the HTML editor window in order for it to take effect. Use the form <dewplayer>filepath/filename.mp3</dewplayer> where file path is the path to the file starting from your personal directory. Do not include a beginning slash. Click "update" on the html editor window when the changes have been made. The tag will simply appear as the filepath/filename.mp3 (without the tags) in the TinyMCE editor but will be converted to the dew player when the page is saved and viewed.

It is also possible to copy and paste the HTML code for a dew player (from a page on recherche.ircam.fr for example) into the HTML editor of TinyMCE, this is not recommended however since it would involve updating the path to the swf file and the mp3 file in several locations. This is the most tedious method!

JW Player: This player allows flv videos to be embedded into a page. To insert the player the <jwplayer> tag should be used, again using the HTML editor. This tag takes much the same form as before, <jwplayer>filepath/filename.flv</jwplayer>. Again the file path should start from the user's personal directory and should not include a preceding slash. Again once the HTML is updated the filepath/filename.flv will be sent to the editor and when the page is viewed the player will be inserted.

Again, it is possible to copy the HTML code for an existing player into the HTML editor but this is even more tedious than the dew player!

Of course, the file browser can be used to upload any thing, not just media. For example, the file browser can be used to upload .html and .css files. In doing so a user could for example upload a .html version of a report they have produced. If all the necessary files linked to the report are included in the same directory, the user can then link to the main .html file to give access to the full report any where on the site.

Files can also be attached to the page, rather than embedded via a link or a media item, using the "File Attachments" section of an edit form for any page. This section provides a typical browser interface for uploading files. Files will be uploaded into a directory in the file system corresponding to the currentmy logged in user's user name.  This directory is NOT the same as the personal directory mentioned above. It is not accessible in the same manner as mentioned above and is not customizable by the user (in terms of creating subdirectories etc). The files uploaded using File Attachments will not be accesible through the IMCE file browser mentioned above. Each file that is uploaded is displayed with its URL so, of course, files can still be linked to and media can still be embedded. For most of these tasks however it is recommended to use the methods described above since it is more flexible for the user. When a file is uploaded there will an option to "list" it. A listed file is displayed at the bottom of the page in a table for download under the heading "Attachments". An unlisted file is not displayed but can be referenced through the provided URL.

The most important option for an uploaded file is to upload a file as "private". This is the main reason a user may want to use the "File Attachments" section and for most other use cases it would be preferable to use the above methods. Setting a file as "private" saves it in the user's directory in a sub-directory named "private". This directory cannot be accessed via the apache server, which will return a forbidden error. Private files can only be accessed on the site by users who have permission to access the page to which the file is attached. If a file is attached to a password protected page then only users who know the password can access the file. This allows a user to attach sensitive files to a password protected page, perhaps with sensitive material regarding the file, and only share the password with trusted individuals, thereby granting access to the page and the file only to these people.

Perceptive Tests

An important example of using the file browser is to upload the necessary files to produce perceptive audio tests. Naturally such perceptive tests are an important part of the research the teal carries out and as such this website allows the tests to be uploaded to its file system and to be easily linked to. This example template perceptive test was created simply by uploading the .php, .html and .css files along with the relevant images and audio to a subdirectory of the user ladyman's personal directory. From there the link was created by highlighting the relevant section of text, going to the link button in the toolbar, accessing the file browser, selecting the main .html form for the test and sending its address to TinyMCE. The files for the test were taken from ftp://wwwas@recherche.ircam.fr/roebel/test_is2010/ .

URL Aliases

The standard urls produced when creating a node (typically in a form such as node/1560) can be over ridden using the "URL path settings" section of a node edit form. In fact, this is automatically taken care of on all content types, so any content created by an authenticated user will have a "clean" looking url, generally in the form "content_type/node_title". A user can however specify their own url. This may be a good idea in cases for example where the node title is very long and a more concise url is desired. For profiles and profile sub-sections a user can simply fill in the "URL path settings" area to specify their custom path. If this field is left empty a path will be created automatically as mentioned above. For other types of content a check box titled "Automatic alias" will be checked by default on creation. If this is left checked, a default url will be provided. To provide a custom url, simply uncheck the box and enter the desired path as before. Rechecking the box will revert back to the default url. Note that the prefix of the alternative path cannot be changed, in order to keep content logically grouped automatically. Each content type has a url prefix. So for example, software pages take a default url in the form "software/page_name". The user may customize the suffix ie the "page_name" section, but the prefix is fixed. The site will notify the user if they are attempting to create an invalid alternate path.

Menu Settings

The Menu Settings section of a node edit form is only relevant for project and software pages since they are the only pages that have their own links in the menu system under "Plan" to the left. For these two content types a menu link is generated automatically based on the title of the page. If the title of the page is changed, the menu link is updated. The menu link can also be overridden manually by changing the "Menu link title" field of the "Menu settings" section. This is especially usefully when the title of the page is long, or contains many characters which are unnecessary for a menu link. The menu link is always updated when the title changes, so changing the title of a page with a manually set menu link will override the changes made by hand.

Different types of content

A note on General and Flexible Media

The idea behind these two content types is to allow the user to create content that can be used for a range of purposes by starting with a very general create form which allows the user to build a page which specifically meets their needs, as opposed to other content types which in general have a very specific purpose (a software page for example must always be used to present an overview of some software). Both General and Flexible Media can be used as demonstrations of work as described in this section and they allow images, audio and video to be uploaded, positioned, sized and embedded easily. User's can make these pages as specific or as broad as they need to. The difference between General and Flexible Media types will be explained below in their respective sections.

These two types of content offer the user some unique options based on the idea that they can be used as demonstrations of work.

The user can choose to set the content to Demonstration or General, they can set the content to be Personal and they can choose whether this content should be Public or Private.

Demonstration or General: This option determines whether the content being created will be displayed in the lists of content that appear on the site. These are found in the "Demonstrations" section, on software forms and on researcher profiles as well as the "Latest Demos" panel. Setting the content to Demonstration indicates that it is being used to demonstrate some thing on the site, for example the workings of a software package. It will cause the content to be automatically referenced in the relevant lists. Setting the content to General indicates the content is to be used for some other purpose and will prevent it from being listed. It can then be referenced using html links. This can be used for example to create a main demonstration page of a piece of software, say a video tour of the interface, which provides links to some audio examples. If the content is set as demonstration it is important to make sure it is tagged properly. It should for example be tagged with the software it demonstrates, if that is appropriate.

Personal: Applying the "Personal" check box on a node indicates that that node will be used in reference to a user's own personal work, as apposed to being used in reference to a more global node like a software page for example. In general, any authenticated user can edit any General or Flexible Media node. Setting one of these nodes to Personal however prevents other users from being able to make changes to the page, ensuring that only the author has the right to edit his or her Personal nodes. Only the author of a node can change the Personal check box. If the node is set as a Demonstration, the Personal check box has the added function of determining which lists the content will appear in. Personal demos are only included in the Activity Demonstrations list of the author's profile page. Leaving the Personal box unchecked indicates that the node is a demonstration of some other piece of content on the site and so will be included in all relevant lists.

Password Protected:  A user may control access to their General and Flexible Media pages by adding password protection. To add password protection see the "Password protect" section of the edit form. The drop-down area provides a check box to apply password protection and a field for the user to provide the password they wish to be used. Protection will be applied when the form is saved. If the content is unprotected any one can access it and it will be displayed in all relevant lists on the site. If the content is protected it will be removed from all public areas of the site. The site will request users and visitors to enter a password when they attempt to access the page, enabling the author to be selective over who they wish to grant access to by sharing the password. The author and site architects will be able to access the page without requiring the password. The author is the only user who has the right to add password protection to a node and the only user who can edit that node once it is protected. 

This feature is useful for example if a user is creating a demonstration to go with an unpublished piece of work that they wish to share only with a select number of people (examiners, advisers, colleagues etc) prior to the work being published. The author is the only user who can make changes to a nodes Public/Private status.

Blog entry

To create a blog entry and add it to your personal blog create a content of type Blog entry. This content type provides a simple create form with a title and body section. Once created the blog entry will be added to your blog list which is accessible via the link in the left menu panel. Anyone can reply to a blog entry by using the comment form at the bottom of the page. New blog entries will be showcased in the right most column.

General Media

A General Media content type provides a very broad page template which a user can then make as specialized as they need to. General Media pages can be used as demonstrations or work both globally or personally and can also be used as private pages. General Media allows images, video and audio to be integrated easily through the main editor interface which also for the easy creation of links and rich text.

Flexible Media

Flexible Media provides all of the functionality of the General Media content type. Where Flexible Media is different is that it provides an interface to create this functionality in "panes", which can be positioned to create columns, rows and sections on a page. A page of type Flexible Media is therefore built up from individual panes of content and is referred to as a panel. The process of creating a Flexible Media page is more complex but ultimately more flexible than creating a General Media page in which the page is created through a typical edit form.

When going to Create Content->Flexible Media the user will be asked to pick the over all lay out of the page. Some default panel layouts are provided which split the page up into various numbers of rows and columns. The "Flexible" setting is a special case which will allow a user to insert a custom number of regions on the page into which they can insert a custom number of panes. The size of each pane and region can be changed through the interface.

Once a user has selected their desired panel layout they will be presented with a typical edit form for the page as a whole. This form will actually create the page once saved and provides the usual fields such as available tags, demonstration settings, outline and so on. Once the form has been saved the finished page will be presented, currently without content. At the top of this view there are two more tabs of interest than the usual View and Edit. Panel Layout allows the user to choose another column/row layout and will present options for resetting any panels that have been created to match the new template. The "Panel content" tab presents the form where users can create, position and edit panels and begin to add content to the page.

The panel content page provides an overview of the panels currently on the page. The page shows named regions which correspond to the columns/rows layout set in the Panel Layout section. To add a new panel to a region click on the image of a cog in the top left corner of that region. The drop down menu displays the settings interface for that region. Clicking add content will open a window from which a user can create a panel. The window allows the user to create various kinds of panes based on existing elements of the site (existing nodes, or fields for example). For most users, the desired option will be the "New custom content" option. Selecting this option presents a reasonably familiar editing window. There is a field to set the title of the pane and also a body field with the rich text editor where the main text of the pane should be entered. Once this is complete, clicking finish will create the pane and return the user to the region overview, with the pain now visible in its region. If multiple panes have been added to a region it is possible to drag and drop them (using the grey handle bar) to change their order on the page. Panes can also be dragged between regions. A cog symbol similar to earlier in the top right of the pane gives access to the pane's menu. To make changes to the pane's body or title fields select "settings" from the menu, which will bring up the edit window presented earlier. The other most useful item in the drop down menu is the "Visibility rules" area. Selecting "Add new rule" allows a user to restrict the situations in which the pane is visible. This allows the user to vary the content of the panel according to the current site language or user status, for example. In order to make any changes to the content of the panel it is necessary to click save at the bottom of the region overview page.

If the user has selected "Flexible" as the Panel Layout type, it will be possible to edit the number and size of the regions themselves on the Panel Content page. To view and edit regions, click on the "Show layout designer" button. The regional layout is disabled as a number of boxes. The main region is the canvas. The canvas is split into a number of columns. Clicking on the canvas drop down icon will allow the user to add a column to the left or to the right of the canvas. Each column is made up of a number of rows. Clicking on the column drop down menu will allow a user to add a row to the top or bottom of the column. Each row is made up of regions which can be added to the left or right of the row in a similar manor. Each column/row/region is separated by a grey handle bar, which can be dragged left/right or up/down in order to change the relative widths or heights of each region. 

Using a Flexible Media content type with a "Flexible" Panel Layout is the most customizable and yet most complex way to create content on the site.

News

A News could annouce an event, modifications on website, or any other fact considered as new. Recent news items will be automatically cycled through in the "News" panel on the left. Clicking on "see today" will show a list of ll news items that were created on that day. Clicking on "see all" will show all the news items currently on the site. News items have an automatic life span of one week. After this time they will be automatically deleted, so users will not have to worry about maintaining the news section. When creating a news item it is necessary to add a title, add your name and the date and time that you are posting on. As with all other content types a language should be selected and, once the news item is finished, a translation should be created.

Project Form

A Project Form is used to display the details of a project that the team is involved in. It requires a title, the date the project started and the project status - whether it is ongoing or finished. Again, a language should be chosen and a subsequent translation added. The "outline" section should be used to give a brief description of the project, to be displayed on the summary project. The body section then allows an in depth description to be given.

Publication

A Publication is used to create a reference on the site to one of the team's internal reports (Conseils Scientifiques, Rapports d'Activité, Projets d'Activité). A publication node is a page that presents a link to the publication (whether its .html, .pdf, .doc etc) and also has space for any notes that are relevant. To create a Publication, the files and/or folders for the report should first be placed into the correct folder by copying them to sites/default/files/publications and then choosing the corresponding folder. Create a Publication node. Ensure that the correct tags are entered in the "Vocabularies" section (the "publication type" tag is used to create the link to the file and the "year of publication" tag is used to create lists of all reports). In the location section should be entered the path from the report type folder (conseils_scientifiques, projets_activites or rapports_activites) to the file (excluding leading and trailing slashes). This may just be the name of the file, for example "report09.html" or, if the main index of a report is part of a larger directory of files and folders, it may be some thing like "report09/index.html". Once the Publication has been saved it will be available from the lists found at Publications->Ircam Reports referenced by the type of report and the year it was written. Multiple reports of the same type, written in the same year will be referenced by, taking 2009 as an example - 2009, 2009-1, 2009-2, 2009-3...

Researcher Profile

A Researcher Profile is used to create a kind of profile page for each member of the team (this does not contain account details). A name should be given for the researcher. A language should be chosen and, as before, a translation created when the profile is complete. The "activities" section should be used to created a list (comma separated for example) of the researcher's current and past activities within the team. This will then be displayed as a summary in the "People" section. In the body can be used to enter a full description of the researcher or a link can be providing using html to the researcher's external site if this is preferred.

Researcher Profile Page

A Researcher Profile Page is an optional extension of the a Researcher Profile. If a relatively large Researcher Profile is to be created it may be desirable to split the profile into a number of distinct sections. This can be achieved by creating several Researcher Profile Pages, as well as the main page. The Researcher Profile Page has a simple edit form and only requires a title and body text. The pages you create will be automatically packaged with your main profile page and a menu item for the package will be generated on each page.

Software Form

A Software Form should be used to enter the details of a software program created or contributed to by the team. The form requires a title and a brief "outline" of the aims of the software. A fuller description can then be given in the "body" section. A language should be selected and a translation created once the form is complete.

Info +

For further informations about Drupal:

• Official website's Home page
• Creating content