deliverable d2.1: modap site v1.0 mobility data …...modap d2.1 – modap web site v1.0 modap –...

MODAP D2.1 – MODAP Web Site V1.0

Deliverable D2.1: MODAP SITE V1.0

Mobility Data Mining, and Privacy

MODAP

Sabanci University Fraunhofer IAIS

CNR - Area Della Ricerca di Pisa Wind Telecomunicazioni SpA

Hasselt University EPFL - Ecole Polytechnique Fédérale de Lausanne

Université de Lausanne University of Piraeus Research Centre

Alterra B.V. National & Kapodistrian University of Athens

University of Milan

Project reference: INFSO-ICT-245410


MODAP – WEB SITE V1.0

Del. no: D2.1

INFSO-ICT-

245410

Version: Draft 2.2 14/02/2011

Deliverable type: R

Classification: RE

Work package and task: WP2

Responsibility: SU

Executive summary:

MODAP (Mobility, Data Mining and Privacy) web site V1.0 aims to create a platform for community building and for sharing resources, and facilitating discussions. The first version of the MODAP site enables registration of new users as well as institutional membership. It provides information about the project and directs the users in reading and sharing content and initiate discussions. As of the first year we have more than 300 users registered to MODAP as of February 14. We have around 20 people from social sciences background. We will work towards having a more balanced community during the second year.


Contents

1. OBJECTIVES OF MODAP WEB SITE ................................................................4

2. SITE STATISTICS ............................................................................................5

3. DESCRIPTION OF MODAP WEB SITE V1.0 ......................................................7

3.1. Main Page ............................................................................................................................ 7

3.2. Left Menu............................................................................................................................. 7

3.3. Top Menu............................................................................................................................. 8

3.4. Content Creation................................................................................................................. 8

APPENDIX A. SETTING UP THE MODAP WEB PAGE .............................................11


1. Objectives of MODAP Web Site

The objectives of the MODAP Web Site can be summarized as follows:

• To create a web platform for the MODAP Working Group members for effective

communication

• To provide a repository for all project related material to be stored/searched and

retrieved easily and effectively

• To be the interface of the project to the outside world with presentation of

selected project material and results

• Provide online training material for researchers

The first version of the MODAP site enables registration of the new users to record and

consolidate the community. It was also designed to enable discussions and content

sharing through news groups blogs and similar media within.


2. Site Statistics

Site statistics of the MODAP web site was shown in the figures below. Figure 1 shows

the daily number of visitors starting from the launch of the MODAP web site. In the

figures the reader will see a peek in November which corresponds to the ACM

SIGSPATIAL conference at the beginning of November when we distributed the

MODAP fliers to a large audience. Also at the end of September there are some peaks

which correspond to the ECMLPKDD conference when we publicised MODAP. The

daily page accesses and the hits of most visited pages shows the general activity within

the MODAP web site in terms of visited pages. In Figure 1, the reader will notice that the

MODAP hits drop in February, this corresponds to the launch of the social networking

site, where we encouraged the community to use the social networking site.

Figure 1: Daily number of visitors


Figure 2: Daily page accesses

Figure 3: Most visited pages


3. Description of MODAP Web Site V1.0

3.1. Main Page

We purchased a server an obtained the www.modap.org domain name for MODAP.

During the kick-off meeting we decided on the logo and the motto of MODAP which is

“Privacy on the move!” to make sure that people remember this motto and understand our

motives. The MODAP site is open to outside, and currently hosts dissemination material

and information about the registered users. The reader will see the main page screen shot

below in Figure 1.

Figure 1: Main page

3.2. Left Menu

On the left hand side we have the main menu that describes the community structure and

the community building activities together with content creation option with registration.


Users can register to the site from the main page and after that they can browse the

community material.

Figure 2: Menu tabs

3.3. Top Menu

The top menu tabs are highlighted in Figure 2 which is shown above. Blogs, Forums are

enabled for users to share their resources, and views with the community. MODAP

sponsored events can also be reached also from the tab menu. Newsletters are an

important media for dissemination for MODAP, therefore we added a link to the PDFs of

the newsletters archive in the tabs menu. Users even without registration can download

the newsletters. Intranet is provided only for the consortium. Resources link are for the

adding training material to the site as well as video and audio material. The resources link

was detailed in Figure 3. As the reader can see we maintain a bibliography for MODAP

related research areas, we plan to include data sets for benchmarking activities, software

related to mobility data mining and privacy, and multimedia- material.

3.4. Content Creation

Content created is facilitated by the menu on the left by pressing the “create content

link”. The new menu that appears for content creation is shown in Figure 5. The user can

choose the type of content that he or she wishes to create such as new blog entry, new

event related to MODAP, new discussion topic, newsletter entry contribution to be edited

by the newsletter editor for possible publication, data set for benchmarking, new software

to share with the community, and internal document to be reviewed within the

consortium, and video content.


Figure 3: Resources

Figure 4: Left menu


The menu on the left side of MODAP web site is depicted in Figure 3. Information about

newcomers who heard about MODAP and interested to learn more about it can be

reached from that menu. We have the short description of MODAP and a short

explanation of our motto “Privacy on the move” which is supposed to live beyond the

scope of the MODAP project. Member institutions are listed as well as the procedure to

join the community as individual and institutional member.

Figure 5: Content Reation


Appendix A. Setting up the MODAP Web Page

In this appendix we provide the implementation of the content management system of

MODAP site V1.0. The system was implemented using an open source content

management system called drupal. The details are reported in the following subsections

of the appendix.

Setting up the MODAP Web Page

Thomas B. Pedersen

December 16, 2009

Contents

1 Configure Drupal 3

2 Setting up the Web Page 32.1 Basic Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2.1.1 Static Pages . . . . . . . . . . . . . . . . . . . . . . . . . . 32.1.2 Search Pages . . . . . . . . . . . . . . . . . . . . . . . . . 32.1.3 Site Information . . . . . . . . . . . . . . . . . . . . . . . 32.1.4 Date and Time . . . . . . . . . . . . . . . . . . . . . . . . 32.1.5 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.1.6 Site Taxonomy . . . . . . . . . . . . . . . . . . . . . . . . 32.1.7 Basic User Profile . . . . . . . . . . . . . . . . . . . . . . 42.1.8 About Menu . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.2 List Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2.1 Static Pages . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2.2 Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.3 Institutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.4 Extended User Profile . . . . . . . . . . . . . . . . . . . . . . . . 82.5 User Blogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.6 Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.6.1 Upcoming Events . . . . . . . . . . . . . . . . . . . . . . . 122.7 Working Group Fora . . . . . . . . . . . . . . . . . . . . . . . . . 122.8 Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.9 Newsletter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.10 Datasets & Software . . . . . . . . . . . . . . . . . . . . . . . . . 152.11 Multimedia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.12 Nice Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.12.1 Real Names . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3 Drupal Concepts and their Use 203.1 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.2 Note Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3 Taxonomy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.4 Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

1

4 Extra Drupal Modules 214.1 Content Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5 Site Promition 22

6 Todo List 22

2

1 Configure Drupal

Set the memory limit to 24 MB by adding the line ini set(’memory limit’,’24M’); to sites/default/settings.php

2 Setting up the Web Page

2.1 Basic Setup

[Caching ]

2.1.1 Static Pages

The first thing we need, is a front page, which can be customised according toour needs. To this end we create a new page (which will be node/1), and writethe HTML code of our front page.

We also need pages for “access denied” and “Page not found.”

2.1.2 Search Pages

To allow search, the module “Search” has to be enables.

2.1.3 Site Information

Next we need to set up some basic information about the webpage. In Admin-ister > Site configuration > Site information we set the name of the webpage,email address of the web-master, and the URL of the front page (node/1, whichwe created before).

2.1.4 Date and Time

Some modules requires that the server timezone is specified. In Home > Administer> Site configuration > Date and time set the time zone to Brussels (it isa EU project). Disable user configurable time zones (so that calendars will notcreate any confusion).

2.1.5 Errors

In the site configuration under error reporting, we can define which pages toshow for “page not found” and “access denied” errors. We should also set errorreporting to “Write errors to log” (and not page!).

2.1.6 Site Taxonomy

Now we create the static taxonomies of MODAP. Go to Home > Adminis-ter > Content management > Taxonomy, and create a new taxonomy named“Working Groups”. Next add each MODAP working group as a term to thistaxonomy.

3

2.1.7 Basic User Profile

In Home > Administer > User management > User settings select “Visitors cancreate accounts and no administrator approval is required,” so that users cansign up easily, “Require e-mail verification when a visitor creates an account,”so that passwords are generated automatically (are secure), and to put an ob-stacle for spammers. Create the directory sites/default/files/pictures/users inthe drupal directory, and enable “pictures.” Set the default path of profile pic-tures to pictures/users, so that all user profile pictures are collected in one paceseparate from other pictures.

2.1.8 About Menu

In Home > Administer > Site building > Menus we create a menu for the“about” pages of the site. The name of the menu is about, the title is About,and the description is “About MODAP and Privacy on the Move.”

The about menu only points to static pages, so we populate the menu bycreating the pages one by one.

The menu points to the pages:

• About Privacy on the Move

• About MODAP

• MODAP Partners

• Working Groups

When creating each of the pages, make sure to select the “about” menu asparent item, and set the menu title to the same as the page title.

To make the menu visible on the main page and about pages go to Home> Administer > Site building > Blocks and activate the “About” blockto the left side bar. Drag the about block to the top, so it occurs before thenavigation and login blocks.

From the “Working Groups” page we will have links to pages with lists ofmembers of each working group. The page is a view:

• Create a new node view with name “working groups,” and description“Working Group Content Lists.”

• Add argument “taxonomy: term.” Choose lower case for “case in path”and check “transform spaces to dashes.”

• Set title for the argument to Members of %1, and wildcard title to “Pri-vacy on the Move.”

• Add a PHP field validator, and add the code $breadcrumb[] = l(’Home’,null); $breadcrumb[] .= l(’Working Groups’, ’content/working groups’);drupal set breadcrumb($breadcrumb); return true;. This will setthe breadcrumb of the view.

4

• Add new field “Node: title.”

• Set items to display to 40, and pager to full pager.

• Add new page display and give it name “Members”.

• In overwrite mode add filter “node: type = Profile.”

• In overwrite mode add add fields “User: photo” (no label), and “User:name” with link to user and label “User”. Remove field “Node: title.”

• In overwrite mode set style to table, sorted by user, and with both fieldssortable.

• Set path of the members page to “members/%”

• Add links to “members/[wgname]” where necessary (e.g. about/working groups).

On the member pages, we will have a link which allows MODAP membersto send mail to everyone on a list:

• On the working groups view above, add a new attachment display withname “Mailto”.

• In overwrite mode, make sure that the only field is User: email, and thatthe filter Node: type = profile is present.

• In attachment settings, choose position after, and attach the attachmentto the members view.

• In general options, set the style to raw (make sure that the Views Addonmodule is activated).

• It is very important to restrict access to users with role MODAP partnersonly!

• In the settings for the raw style, set prefix to <a href=’mailto:?bcc=,row seperator to ’,’, and postfix to ’>Send mail to everyone on thislist</a>.

[It seems like the more link does not work on the members list.][The mailing list link on a member page probably only gives the emails of the

people on the current page. This is a problem if the member list is more thanone page long! ]

2.2 List Page

On the web page we will need several lists of content. A powerful way of doingthis is with the contributed Views module. The list view is set up as follows.

First activate the Views module.

5

On the Home > Administer > Site building > Views page, create anew view with name “content list,” description “List nodes of given contenttypes and terms,” and type node.

On the view edit page, first add two arguments: “Node: type” (with defaultvalues), and “Taxonomy: Term.” For the term argument, check “Transformspaces to dashes in URLs” and choose lowercase in “Case in path.”

Change the row style to node. Add filter “Node: Published = yes.”To actually display the lists, we need to add a page display. Give it the path

“list/%/%”.Finally save the view.This view is very powerful, since the url /list/all/all will not show ALL con-

tent on the web page. So it is very important that all content which should notbe seen by outsiders has a view restriction. [Refer to description of restrictions.]

2.2.1 Static Pages

The site contains a few static pages. ¡dl¿ ¡dt¿Resources¡/dt¿¡dd¿This page linksto other pages with resources such as the bibliography, benchmarks, software,e.t.c. This page is linked to the “primary links” menu.¡/dd¿ ¡/dl¿

2.2.2 Roles

In Home > Administer > User management > Roles we add the following roles:

anonymous user Default Drupal role, who does not have an account. Anony-mous users only allowed to read content. They can read all content exceptthe intranet.

authenticated user Default Drupal role. Anyone is allowed to create an ac-count. An authenticated user is only allowed to write comments to existingcontent. [Refer to the signup procedure. We require email verification forauth users.]

contributing user A contributor is a user who is an active member of theMODAP community. Contributing users will have their own blog, andwill be able to submit newsletter articles, datasets, software, and othercontent to the web site.

modap partner A partner is a MODAP project partner. Partners have accessto the intranet.

editor Editors set up news issues of the newsletter, review and select articles,and finally release the newsletter issues.

administrator A user with privileges to administrate user accounts.

web-designer A user with privileges to change the theme and menu structureof the site.

6

We use roles in an “incremental” way. A specific permission is only given toone role. Because of this, it does not make much sense to be a partner, withoutalso being authenticated user, and contributor.

[Describe permissions! ] [Give anonymous users permission to read com-ments! ]

2.3 Institutions

MODAP has a number of partners in the consortium, and some associatedpartners. New partners can be added as the project progresses. To allow dy-namic addition and listing of associated partners, we define a “content type”for associated partners.

Required modules:

• CCK

• Option widget (part of CCK)

• User reference (part of CCK)

• Link (CCK extension)

• Views

Create content type:

• In Home > Administer > Content management > Content types adda new content type with name “Institution,” and type institution.

• In Submission form settings, set title to “Institution name,” and removebody field.

• In comment settings, disable comments.

• Manage fields of institution.

• Add a user reference field with label “Contact person,” and title contact.Make the form element “autocomplete text field.” Make the field required.

• Add a text field with label “Institution type” and title institution type.Select the form element “radio buttons.” On the settings page make thefield required, and set the options “In consortium” and “Associated Part-ner.”

• Add a link field with label “Url” and title url. In settings select “Notitle” as link title option.

• Add a text field with label “Comment” and title comment. Give the fieldhelp text “Comments about the institution (e.g. ”Coordinator of theApplications working group”).”

7

Create views:

• In Home > Administer > Site building > Views add a new node-type view with name institutions and description “List of institutions.”

• Add filters: Node: published = yes, Node: type = Institution.

• Add fields: Node: title (no label, rewrite field to set ¡strong¿ tag arroundtitle), Content: contact person, and Content: url (no label).

• Set style to HTML list, unordered. Set items per page to 0 (unlimited).

• Add a new block display. Give it name and title “Consortium.”

• In overwrite mode add a filter to the consortium block: Content: institu-tion type - allowed values = In consortium.

• Add another block display. Give it name and title “Associated Partners.”with overwrite filter: Content: institution type - allowed values = Associ-ated Partner.

MODAP Member Institutions page:

• Create a new page with title “MODAP Member Institutions” (write downthe url of the node).

• Go to Home > Administer > Site building > Blocks, and configurethe two blocks “institutions: Consortium” and “institutions: AssociatePartners”. Select “Show only on listed pages”, and make the new MODAPMember institutions page the only page to show the blocks on.

• Place the two blocks on the content region, and make sure that Consortiumis at the top.

[Permissions: Only administrator can create, delete, and edit institutions.]

2.4 Extended User Profile

By default, Drupal only require a user to choose a user name, and inform hisemail address. However, we also want to give users the ability to give their realname, a photo, affiliation, and primary interests (working group).

To make the extended user profile, we use the content profile module (see4.1). When the content profile module is installed, a new content type will beavailable: profile. We have to customise the profile content type to our needs.Go to Home > Administer > Content management > Content types (hence-forth the profile content type page) and edit the profile content type. In theSubmission form settings remove the body field label, so that users will not haveto write any free text in their profiles (we have no use of that). Make sure thatwork-flow settings do not promote new profile nodes to the front page. Disablecomments. Make sure that the profile content type is used for user profiles in

8

the Content Profile form. The default description of a profile is “A user profilebuilt as content.” We change that to something more meaning full: “Set yourreal name, main interests, e.t.c. in your ¡em¿user profile¡/em¿.”

By default the user has to write a title for his profile page. However, wewant all profile pages to have the title “User profile of [user name]”. To do this,we use the auto nodetitle module. Make sure that the token and auto nodetitlemodules are installed, and open the “Automatic title generation” form on theprofile content type page. Select “Automatically generate the title and hide thetitle field.” Set the pattern to “Profile for [autho-name].”

In articles, blog entries, e.t.c. we want the ability to show the users realname. The user should be able to write his real name (not login name) on theadvanced user profile page. The module CCK allows us to add extra fields tonodes (based on their content type). Make sure the CCK module is installed,and that CCK - text is activated in Home > Administer > Site building> Modules. In the profile content type page, select “manage fields.” Add anew field with label “Real name,” and name “real name.” Select type “text”and form element “text field”. After saving, accept all the default values onthe properties page, but write a helpful text like “Enter your real name” in thehelp text. On the Profile “manage fields” page, drag the new real name fieldup to right after the title (and before taxonomy). Also create a text field calledaffiliation. Give the help text “Your university or company.” Drag it up, so itis right after real name.

We have to set appropriate permissions to allow users to create and edit theiruser profile. Go to Home > Administer > User management > Permissions.In the authenticated user column, enable “create profile content,” “delete ownprofile content,” and “edit own profile content.”

[On the profile page, the working groups are shown as tag of the page. Wecould use a custom content type theme page to show them as a list with the title“main interests”.]

2.5 User Blogs

Contributing users (see 2.2.2) will each get their own blog, where they canpost non-reviewed information they find relevant for the community. To enableblogging, go to Home > Administer > Site building > Modules and en-able blog. Only contributing users should have their own blog, so go to Home >Administer > User management > Permissions and make sure that “createblog entries,” “delete own blog entries,” and “edit own blog entries” is activatedfor contributing users (and only for contributing users). To ease the work ofthe main site administrator, we also enable “delete any blog entry” for theadministrator role.

The default description of a blog entry is “A ¡em¿blog entry¡/em¿ is a singlepost to an online journal, or ¡em¿blog¡/em¿.” We change that to somethingmore meaning full: “Add a new entry to your ¡em¿blog¡/em¿.”

We want blogs to be tagged with the working groups of interest, plus auser defined list of tags ([for the tag cloud ]). [ref working group vocab]. In the

9

Home > Administer > Content management > Taxonomy edit the “WorkingGroups” vocabulary, and add “Blog entry” to the list of content types. Createa new vocabulary called “Tags” and select “Blog entry.” Set the option “tag.”[tag also applies to discussion]

[attach recent blogs (with more link) to web page.][Add Active Bloggers block.]

2.6 Calendar

We use the Drupal Calendar module to create an event calendar for the web site.The calendar is also used to tract activities arranged by the MODAP project.This helps in the reporting.

Required modules:

• Views

• Date

• Date API

• CCK

• Calendar

• Rules

• Rules Administration UI

• Rules Forms Support

We need a new content type which users can use to create a new event. Goto Home > Administer > Content management > Content types, and adda new content type. The name of the new content type is Event, and the typeis event. As description write “Add a new ¡em¿event¡/em¿ to the calendar.”In the submission form settings, change the label Title to Event, and the la-bel Body to Description. On the Home > Administer > User management >Permissions page we set “create event content,” “delete own event content,”and “edit own event content” permissions for contributing users, and “deleteany page content” for the administrator role.

We need users to specify start and end time of events, so we add a CCK fieldin “manage fields” on the event content type page. The label of the field is Date,the field name is date, the type is Date, and the form is text field with custominput format. On the properties page set the custom input format to “Y-m-d.”Set the help text to “Please specify the start and end dates of the event.” Makethe field required, and to date optional. In granularity select year, month, anddate. Finally deactivate time zone handling. If times are change according totimezone, confusion can occur. The time is normally specified relative to thelocation of the event. In the Event content type page, move the date field upto right under Event (the title), before Description.

10

We want users to be able to tag events by relevant working groups. In Home> Administer > Content management > Taxonomy edit the working groupvocabulary. Check Event in the content type list.

If the event is created by a MODAP partner, the user should indicate ifthe event is arranged by MODAP. The possible event types are “Working groupmeeting,” “Working Group event,” “Work Package Meeting,” “Board Meeting,”or “other.” We add a new CCK field to the content type to store the event type.Add a new text field with label “Event type” and name event type. Set theform element to select list. In the settings of the field, add help text whichexplains the different event types. Make the field required. Write the aboveevent types one per line in the allowed values list. Save the field, but edit itagain, so that you can set the default value to “other” (this will be set by eventcreated by non MODAP partners). Drag the event type field to right after thetaxonomy field, and save.

We need to make sure that only MODAP partners can set the event type.We do this by adding a rule which hides the event type field for all non MODAPpartners. First we need to go to the “form events” menu in Home > Administer> Rules. Check “Enable event activation messages on forms,” and save. Nowcreate a new event in create content (do not save it). At the top of the CreateEvent page, there will be a link “Activate events for event node form” Click thelink, press activate, uncheck “Enable event activation messages on forms,” andsave. Now go to triggered rules in Home > Administer > Rules. Add a newrule with lable “Hide event type from non partners.”. In the event pulldown,choose “Event node form is beeing build.” As category you can put “calendar.”Save changes. On the next page, add a new condition. Select “user has role.”On the next page, check negate, and select the rule MODAP partner. Give thecondition the name “User is MODAP partner” (event though we want NONpartners, you will see why). After saving the condition, add a new action.Choose “Hide an element of the form” As form id write field event type(which was the name we choose for the field in CCK). Save. Now only MODAPpartners can change the event type to something else than “other”.

Calendar uses the views module to show a nice calendar. In Home > Administer> Site building > Views, activate the calendar view. The default calendarview will show a calendar with all updates of all content on the site. Sincewe only want an event calendar, we clone the default calendar. Give the newview the name event calendar, and set the description to something meaning-ful: “Event calendar.” Add a new filter which filters on node type, so that onlyevent type nodes are shown.

By default the calendar shows the event by the date of their last update.We have to change that, so that the events are shown on their start date (andthroughout their duration). Edit the argument Date. In date field, change theselection from updated date to field date from date. This will give some errors,but do not worry. Next we add a field. Again select from date. Make sure thereis no label. Now the error should be gone again. Remove the old update datefield.

Events are still sorted by their update date, so add a new sorting criteria.

11

Select from date, and sort ascending. Then remove the old sorting criteria.Do not forget to press save before you leave the views page! Deactivate the

default calendar view again.[Attach the calendar to the web site.][Check that lists show all events (and not only the first 10)]

2.6.1 Upcoming Events

We extend the event calendar view to include a page which lists upcomingevents. Go to the event calendar view page, and add a new display of typepage. Change the name and title to “Upcoming events.” Change the style to“HTML list,” and row style “fields.” Set path to [“upcoming”]. Edit the “emptytext”. Make sure you use overwritten values! Then set the text to “There areno upcoming events in the calendar.” Set the menu to normal menu, and write“Upcoming Events” in the title field. Attach the menu to [primary links]. Tomake sure we only list future events, we add a new filter of type Date (node).Select the date field “from date” and press update. Then write now in the datedefault field, and select the greater than equal operator, and press update.

Do not forget to save the view before leaving the view page!

2.7 Working Group Fora

Each working group should have its own message board where everyone inter-ested can participate in open discussion. Drupal has a build in forum function-ality, which, however does not satisfy our needs. The shortcomming of drupalforum is that it creates its own vocabulary in the taxonomy. A user will thushave to tag a new discussion with the name of the working group twice: onceto select the drupal forum, and once to make the discussion appear on lists ofcontent related to that working group (together with blogs, papers, and othermaterial). Another shortcomming is that the forum lost will show all fora (onlyone content type supports drupa forum), so we cannot have internal fora in theconsortium which are inaccessible to outsiders.

To overcome the shortcomings of drupal fora, we have created our own forummodule. It is activated in Home > Administer > Site building > Modulesby activating “Taxonomy forum.” Before configuring taxonomy forum, we needto create the vocabulary for the working groups [ref ], and a content type forforum topics.

Create a new content type in Home > Administer > Content management> Content types. Name it “Discussion,” and give it type “wg discussion.”Give it the description “A ¡em¿discussion¡/em¿ is the initial post to a newdiscussion thread within one or more working group message boards.” Changethe title field to “Topic.” Disable promotion to front page. Important: inorder for people to be able to answer on new topics, commenting should beenabled for the content type. The default values are ok.

We have to make the working group taxonomy available to discussions byadding wg discussion to the Working Group vocabulary in Home > Administer

12

> Content management > Taxonomy.In Home > Administer > User management > Permissions we allow con-

tributing users to create new forum topics by giving them the permissions “cre-ate wg discussion content,” “edit own wg discussion content,” and “delete ownwg discussion content.” We need to give all users permission to list forums bygiving the permission “access taxonomy forum content” to anonymous users andauthenticated users. Finally we give the administrator permission “delete anywg discussion content.”

Finally we need to configure the taxonomy forum module in Home > Administer> Content management > Taxonomy forum. Select content type discussion,and vocabulary working groups.

A list of working group fora is now available on the url board. We addthis link to the primary links in Home > Administer > Site building >Menus with the title “Working Groups.” Set the description to “Working Groupdiscussion boards.”

2.8 Bibliography

We keep a bibliography online at bibsonomy.org. To show the modap bibliogr-pahy in the modap.org page, we activate a cusom drupal module “BibSonomy”on the Home > Administer > Site building > Modules page. In the Bib-Sonomy module configuration page we have to set the username of the bibson-omy user/group, and an API key (which you can get from the settings tab onbibsonomy). To make the bibliography visible to users, grant “access bibson-omy list” permission to the anonymous and authenticated user roles in Home >Administer > User management > Permissions.

2.9 Newsletter

[This is work in progress! ]Enable the following modules:

• “book” from core.

• “Option Widgets” from CCK.

• “Workflow,” and “Workflow access” from the Workflow contributed mod-ule.

Create newsletter content type:

• Add content type with name “Newsletter entry,” and type “newsletter entry.”Set the description to “Add a new entry to the upcoming issue of thenewsletter.”. Disable comments.

• In the settings tab on Home > Administer > Content management >Books, add “newsletter entry” as allowed book outline type, and set it todefault child type.

13

Create newsletter work flow:

• Go to Home > Administer > Site building > Workflow, and add anew workflow with name “Newsletter.”

• Create the states: Draft, Needs approval, Needs work, Approved, Pub-lished.

• Assign the Newsletter workflow to the newsletter content type (on thesame workflow page), and then save workflow mapping.

• Press the edit link of the newsletter workflow to go to the workflow tran-sition page.

• In the first row of the table, we will select which users can create newnewsletter entries, and which state they can put them in. Here we allowauthors to create newsletter entries in draft state, and the editor to createnewsletter entries in approved state.

• In the next row we grant authors the right to change state from draft toneeds approval.

• In the third row we grant the editor right to change from needs approvalto approved, needs work, and published.

• Also give the editor right to move from approved to published, and theauthor right to move from needs work to needs approval.

• In the access control box we make sure that only contributing users andeditors can view, edit, and delete nodes in the states draft, needs approval,and needs work.

• We allow both contributing users and editors to see nodes in the approvedstate, but only the editor can edit and delete nodes in this state.

• Finally both anonymous users and authenticated users can view nodes inthe published state (but no one can edit or delete).

Create newsletter views:

• Create a new node view with name “newsletters”

• Add the filters

– Node: published - yes.

– Node: type - Newsletter entry.

– Book: depth - 1.

– Workflow: current state - Published.

• Add field “title,” and link it to node. Also add field “workflow: previoustime,” with label “Issued.”.

14

• Set the style to table, allow sorting on all fields, but set default sorting toIssued field, descending.

• Create new page display. Give it title “Newsletters,” path “newsletters,”and link it to primary-links menu.

• Create new block display. Give it name and title “Upcoming issue”. Inoverride mode change the filter “workflow = published” to “workflow isnot published,” and set access to require “create newsletter entry” per-mission.

• Do not forget to save the view!

• In the blocks configuration add the “newsletters: next issue” block tothe content block. Configure the block so that it only shows up on thenewsletters URL. Give the block the title “Upcoming Issues.”

Newsletter navigation:

• Go to the blocks page (Home > Administer > Site building > Blocks).

• Assign the “Book outline” block to the left sidebar, drag it to the top ofthe list, and save.

• Configure the book outline block, and check “show block only on bookpages.”

Permissions:

• Grant “create newsletter entry,” “delete own newsletter entry,” “edit ownnewsletter entry,” and “add content to books” permission to contributingusers.

• Grant “administer book outlines,” and “create new books” permission toeditor.

• Grant “access printer-friendly version” to anonymous and authenticatedusers.

2.10 Datasets & Software

Contributing users have the possibility of uploading datasets which can be usedfor benchmarking.

Activate the following modules:

• “Number” module from the CCK contributed module.

• “FileField” from the FileField CCK extension module.

• “Views”

Create content type:

15

• Create new content type with name “Data set” and type dataset. Giveit the description “A ¡em¿data set¡/em¿ is a file with location and/ormobility data (trajectories, road maps, points of interest) which can beused for benchmarking.”

• In the submission form settings tab, change title label to “Name” and bodylabel to “Description.” Set the submission guideline to “Please make surethat you give a detailed description of the nature and format of the dataset. If your data set consists of more than one file, then pack them in azip or tar file.”

• Add new taxonomy vocabulary with name “Data type.” Give it descrip-tion “The type of data, e.g., road segments, trajectories, GSM cell trans-fers.” Give it the help text “A comma-separated list of terms describingthis content. Example: ”road segments”, trajectories, ”GSM cell trans-fers”.” Check dataset in content types, and tags in settings. Check tag insettings.

• In the Manage fields tab of the content type page for dataset, add thefield “Number of entries” with field name “nr entries.” Set the field typeto Integer and form element to text field.

• Add field “Dataset” with field name “dataset”, and type file. Give thefield help text “Please upload a file containing the dataset.” Make thepermitted file extensions field empty to allow all file extensions. In filepath write “datasets.” Make the field required.

• Give the number of entries field the description “The number of entries inthe data set.” Set the minimum allowed number to 0.

• In the manage fields tab of the content type, rearrange the order of fieldsso that tile is on top, followed by: description, number of entries, and file.

Increase maximum allowed file size:

• Open the file drupal/.htaccess.

• Find the block <IfModule mod php5.c>.

• Add the two lines php value upload max filesize 50M and php valuepost max size 100M.

Permissions:

• Grant create, edit own, delete own permissions for the dataset contenttype for contributing users.

Adding data set list to the web page:

• The content list view from section 2.2 shows a list of all datasets on theURL /list/dataset/all. Add this URL to the resources page.

16

A software content type is created the same way as the dataset content type.Except that we use a vocabulary called “Platform” with the fixed terms: Linux,Windows, Mac, and other. Software has a “license” text field. The Softwarecontent type is used with the working group vocabulary.

2.11 Multimedia

Contributing users will be able to embed videos from various external videoproviders (youtube, e.t.c.) on the modap site. The procedure is very similar todata sets and software as described above, except that a link (or embed code)to the external video is given instead of a file containing data or software. Eachvideo can be tagged with the relevan topic (working group), plus an indicationof whether the video is produced by MODAP or not (necessary for reporting).

Required modules:

• CCK

• Embedded Media Field (CCK extension)

• Embedded Video Field (from the Embedded Media Field module)

Create Video content type.

• In Home > Administer > Content management > Content types adda new content type with name “Video” and type video. Put a descrip-tion like “Embed a ¡em¿video¡/em¿ hosted at youtube, vimeo, or certainother video sites. It will be possible to view the ¡em¿video¡/em¿ on themodap.org web site.”

• In submission settings, change the body field label to “Description,” thensave the content type.

• From Home > Administer > Content management > Content types clickon “manage fields” of the video content type.

• Add a new field with label “Video” and name video, choose type embed-ded video. On the settings page, after saving the field, select the desiredvideo sites (blip.tv, vimeo, and youtube), and make the field required.

• MODAP partners should be able to indicate that the video is a “modapproduction.” Add a new text field with label “Provider” and name provider.Choose single on/off check box widget. On the settings page set the field asrequired, and add the two allowed values “Contributed” and “MODAP.”Set the help text to “Check this field is the video documents a MODAPevent.”

We want to tag videos with relevant working group. If the submitter is aMODAP member.

17

• In Home > Administer > Content management > Taxonomy edit theworking group vocabulary. Add video as a content type.

• Go back to the manage field tab for the video content type, and make sureor rearrange the fields so that they come in the order: title, taxonomy,video, provider, and description.

We need to hide the “provider” field for non-MODAP partners, so thatvideos will not be falsely reported in a MODAP deliverable.

• Go to forms events in Home > Administer > Rules. Enable event ac-tivation messages. After saving, create a new video (but do not save it).On the top of the video editing page, click the link: Activate events forvideo node form. Disable event activation messages again.

• Go to triggered rules in Home > Administer > Rules. Add a new rulewith label “Hide provider field”. As event select “Video node form is beingbuild.”

• Add a new condition “user has role = MODAP partner”. Check negate(so that only NON MODAP partners will trigger). Give the condition thelabel “User is modap partner”.

• Add a new action “Hide an element from the form”. As form element idwrite field provider.

Permissions. Only content providers should be allowed to post videos (MODAPpartners are supposed to have the role content provider as well).

• In Home > Administer > User management > Permissions give thepermission create, delete own, edit own video content to contributingusers. Give edit any and delete any permission to the administrator role.

View. We create a view which gives a nice grid of available videos.

• In Home > Administer > Site building > Views create a new nodetype view with name and description Videos.

• Add filters “Node: type = Video” and “Node: published = yes”.

• Add field “Node: title”. Check “link to node”. Remove the label.

• Add field “Content: video.” Check “link to node”. Choose no label, andformat “Image thumbnail with link to node.”

• In basic settings, set the style to grid. Set number of columns to 3. Setitems to display to 18. Select “create more link”.

• Add a new page display. Set the path to videos. Select “use page” (full).

Attach to the site:

• Edit the resources page, and add a link to [the view ]

18

2.12 Nice Path

We use the contributed Pathauto module to create nice-looking URLS (insteadof the default node/nn style URLS). This is a must if, for instance, we wantgoogle news to refer to our newsletter.

Required modules:

• Activate the core “Path” module.

• Activate the Pathauto contributed module.

Setting up pathauto.

• In Home > Administer > Site building > URL Alias, go to the au-tomated alias settings tab.

• Set Seperator to “ ”.

• In punctuation settings set the action for underscore to “No action.”

• In node path settings set the following node path settings:

– Default path: content/[title-raw]

– Blog entry path: blogs/[author-name-raw]/0[nid]-[title-raw]

– Dataset path: dataset/0[nid]-[title-raw]

– Discussion path: board/[term-raw]/0[nid]-[title-raw]

– Event path: events/[field date-date]/[nid]

– Newsletter entry path: newsletters/[bookpath-raw]/[title-raw]

– Profile path: user/[author-name-raw]/profile

– Software path: software/0[nid]-[title-raw]

• In taxonomy path settings set working group path to: [vocab-raw]/[catpath-raw] (warning, this means that the paths /working grous/* are reserved!)

• Check “bulk generate aliases.” in blog, node, and user path settings.

• Save configuration.

• When done, go back to Pathauto settings and set “Update action” to “Donothing” (otherwise nodes may change name from time to time, makingold links dead!). If you later want to bulk change aliases, you can tem-porarily chage to “Create new. Delete old.”

19

2.12.1 Real Names

Most content by default shows the login name of the author. To change thisinto the real name of the author, we use the realname module.

Required modules:

• Realname

• Content profile (The steps of section 2.4 needs to be completed before thissection will work).

In the general settings of the realname module check “Show realname innodes”, “Overwrite user fields in view to show realnames.” In the modules set-ting tab of the realname settings page, choose the Content profile module. In thefields tab, select “real name.” Finally go to the recalculate names tab to rebuildall names. In Home > Administer > User management > Permissions giveuse real name permission to anonymous and authenticated users.

3 Drupal Concepts and their Use

3.1 Nodes

In Drupal almost all pages are called nodes. A node is referred to by the URLmodap.org/node/n, where n is the node-id (the unique key of the node in theunderlying database).

3.2 Note Types

[]

Page We only use page to create static pages. No user can create pages, onlythe administrator.

3.3 Taxonomy

Drupal has a build in taxonomy system. All Drupal nodes can be classifiedaccording to one or more taxonomies. This makes it possible to list all contentof the web page which falls in specified classes. In MODAP we will use severaltaxonomies: one to label nodes with their relevant working groups, [more]. Toset up a new taxonomy, a new vocabulary is created in Home > Administer >Content management > Taxonomy.

3.4 Roles

Drupal has build in support for role based access control. We use this to docontrol access to writing comments, writing blogs, publish the newsletters, andaccess the intranet. For each node type, role pair the administrator can setread, create, and edit permissions.

20

4 Extra Drupal Modules

We use the following Drupal modules to improve the functionality of the site:

Content Profile We use this module to collect extra information about users,such as real name, affiliation, and primary interests (working group).

Token Token is a module which is used by many other modules (AutomaticNodetitle, []) which allows pages to have variable texts (tokens) which aresubstituted dynamically with run-time information (like current user).

Automatic Nodetitles “auto nodetitle” is a small and efficient module thatallows hiding of the content title field in the form. To prevent emptycontent title fields one can configure it to generate the title by a givenpattern (relies on ’token’). We use auto nodetitle to set the title of theprofile page to “User profile of [author-name]” (where the token modulesubstitutes [author-name] with the name of the user which creates theprofile page).

Content Construction Kit (CCK) The Content Construction Kit allowsyou to add custom fields to nodes using a web browser. We use CCKto add “real name” field to the advanced user profile. [file fields to bench-marks... ]. CCK is required by the module date.

Views The Views module provides a flexible method for Drupal site designersto control how lists and tables of content are presented. Traditionally,Drupal has hard-coded most of this, particularly in how taxonomy andtracker lists are formatted. Views is required by the module Calendar.[and possibly our own views! ]

Date The date module is a flexible date/time field type for the cck contentmodule. Date is required by the module Calendar.

Workflow The workflow module allows the creation and assignment of arbi-trary workflows to Drupal node types. Workflows are made up of workflowstates. For example, a workflow with the states Draft, Review, and Pub-lished could be assigned to the Story node type. We use for the newsletter.

FileField FileField provides a universal file upload field for CCK. We use itfor uploading datasets and software (into different folders).

PathAuto The Pathauto module automatically generates path aliases for var-ious kinds of content (nodes, categories, users) without requiring the userto manually specify the path alias.

Link A CCK content field which lets you add a complete link to your contenttypes; including URL, title, and optionally a target attribute. We use linkon the parter pages[ and on links of interest page].

21

Realname The RealName module allows the administrator to choose fieldsfrom the user profile that will be used to add a ”real name” element(method) to a user object. With the realname module we can show thereal names of people instead of their modap login.

Embedded Media Field This extensible module will create fields for nodecontent types that can be used to display video, image, and audio filesfrom various third party providers. When entering the content, the userwill simply paste the URL or embed code from the third party, and themodule will automatically determine which content provider is being used.When displaying the content, the proper embedding format will be used.

To improve the modap website, we have the following custom modules:

Taxonomy forum An alternative to the drupal build in forum module, whichallows the administrator to use and existing vocabulary as forum names,instead of creating a new vocabulary. This allows us to use the “workinggroups” vocabulary to define forum titles (so that there will automaticallybe a forum for each working group, and so that forum posts are listed onthe page showing everything related to a working group).

BibSonomy A module which integrates the bibsonomy.org API with Drupal.It provides the page /bibsonomy which shows all the references of a specificuser/group from bibsonomy.org.

Views Addon Extentions to the views module. A new “raw” style to give theadministrator full control over how a view is displayed. Used to createmailto links for mailing lists.

4.1 Content Profile

By default user profile pages are not nodes like other pages. This module allowseach user to specify a user profile which is a node. We use this to collectextra information about users, such as their real name, affiliation, and primaryinterests. While the standard Drupal user profile can be used to keep real nameand affiliation, it cannot use taxonomy, so there is no clean way to let usersselect his primary working group (working groups is a vocabulary in the Drupaltaxonomy [see ...]).

5 Site Promition

6 Todo List

Graphical design related:

• On the profile page, when selecting working group, it should say “Memberof the following WGs.”

22

• Authors should show up under their real name, and not login name.

23

deliverable d2.1: modap site v1.0 mobility data …...modap d2.1 – modap web site v1.0 modap –...

Documents