Project MEE-KAARTEN. Beknopte beschrijving van het systeem & use case. Dirk Derom. t.a.v. Liesbeth Huybrechts

Project MEE-KAARTEN Beknopte beschrijving van het systeem & use case

Dirk Derom t.a.v. Liesbeth Huybrechts 28 november 2010

Inhoudstafel 1 Vereisten van het systeem voor BNA-BBOT...........................................................................3 2 Design van het systeem...........................................................................................................3 3 Use Case .................................................................................................................................4 3.1 Overall scenario................................................................................................................4 3.2 Short data description.......................................................................................................6 3.3 User story..........................................................................................................................7 3.3.1 Browser-based app (Drupal).....................................................................................7 3.3.2 Browser-based app (CollectiveAccess)..................................................................10 3.3.3 Mobile App...............................................................................................................10 3.4 Other functionality...........................................................................................................11 4 Overige systemen..................................................................................................................11

BNA-BBOT Lakensestraat 119, 1000 Brussel, tel: 02/223.21.51 2 / 11 page(s)

1 Voordelen van combo Drupal/CollectiveAccess Volgende lijst is een opsomming van de vereisten en voordelen van de combinatie DrupalCollectiveAccess.. • Robuuste archivering (CollectiveAccess) • Flexibele bewaring van data • Geïntegreerde metadata (incl. OAI) + kernwoorden • Scheiding intern/extern systeem • Sterke ACL • Export/import • Voorkeur voor lokale expertise • Cartografie module • Flexibele ontsluiting (Drupal) • Optie voor metadata • Multi-site • Multi-language • Makkelijk aanpasbaar systeem voor admins: niet importeren van ongewenste velden (vb. privacy) of templating voor specifieke doeleinden (vb. project pagina's) • Makkelijk systeem tav eindgebruikers • Cartografie makkelijk implementeerbaar • Algemeen • Open source: uitbreidbaar en makkelijk(er) inwisselbare ontwikkelaars dan bij commerciële systemen • Grote community • Internationale community • Kostprijs systeem 2 Design van het systeem • Huidige systeem: Stories Matter


• Server waarop een Adobe Air en Drupal synchroniseren. Data wordt overgedragen naar zowel de desktop (Air) als web (Drupal). De module en API werd in opdracht van BBOT ontwikkeld. • Desktop (Air) vergt veel onderhoud, Drupal ontwikkeling is voornamelijk de ontwikkeling van de module • Archivering en integratie met andere systemen is minder evident • Planning van het systeem (wordt nog verkend) • Systeem • Drupal als web interface, CollectiveAccess voor bewaring, Drupal port via AppCelerator naar Android/iPhone en iPad • Data input via CollectiveAccess • Partners • Mogelijkheid om BBOT database te gebruiken, of gescheiden installatie van zowel CollectiveAccess als Drupal • Mogelijkheid om training en ondersteuning te krijgen voor het systeem • Output • Open source en gratis systeem met permissieve licentie • Mogelijkheid voor organisaties om data op onze servers te bewaren • Mogelijkheid voor begeleiding en ontsluiting van de data • Uitgebreide documentatie over systeem en handleiding voor site admins • Consortium voor langere termijn ondersteuning (cf. na het aflopen van het &-jarig project MEE-KAARTEN) 3 Use Case Volgende use case is een 'user story' zoals ze gestuurd wordt naar ontwikkelaars. Dit ter aanvulling van de meer algemenere termen van hierboven. Onderstaande is in het Engels, gezien de offertes niet enkel aan Vlaamse bedrijven gevraagd worden. 3.1 Overall scenario The system consists of a design where a Drupal and CollectieveAccess install syncs both ways. The following users are of importance: BNA-BBOT Lakensestraat 119, 1000 Brussel, tel: 02/223.21.51 4 / 11 page(s)

• Super administrators • Administrators • Moderators • End-Users The database is 'media'-centric, where various media are uploaded, connected with the geo-location, connected with various users and connected with various categories. An overview of the general design is visualized in the following diagram:

Diagram 1: overall design Diagram 1 'overall design' presents the following (potential) scenarios: • Backbone of the system • The CollectiveAccess is the backbone system, where all data is pushed (eventually) OR another system is used to serve as backbone (cf. 'other systems' in diagram) • system used to review data • Drupal is used to display the data and uses the potential of the CMS with regards to theming, display and usability


• syncs with backbone • used to pull data from mobile • used to review and admin data (can be different from backbone) • Mobile • used to display data • potentially used to publish data • most likely does not sync (for limited memory) for offline view 3.2 Short data description The following diagram describes the overall design of the data stored in the system(s):

Diagram 2: data description As previously stated the data is built around the storage of media files (either audio, video, text or images). The following briefly describes the various media types and other data types. • Media • various media files are stored (video, audio, text, images). Needs to be assessed whether these are e.g. in Drupal different content types or whether they are part of one BNA-BBOT Lakensestraat 119, 1000 Brussel, tel: 02/223.21.51 6 / 11 page(s)

bulky media type. • dependent on various media files (e.g. audio vs image) different fields are required (e.g. transcripts for audio and not for images) • media files are linked with all other data types (geo-location, categories and profiles). They can also be linked with other media files (e.g. when a user posts a 'reaction' or 'response' to another media file). (cf. linked with) • examples of fields: title, description, transcript... • Geo-location • geo-locations are lat-lon coordinates or pre-defined areas (e.g. a suburb) • they are referred to in relation with media files or categories • most important fields: lat-lon coordinates, description box, title... • Categories • categories can be considered as folders, organizing the content • they can refer to other categories using a role (e.g. is part of) • most important fields: title, description... • Profiles • profiles are used to describe individuals • they are referred to in relation with media files • main fields: first name, second name, telephone... 3.3 User story 3.3.1 Browser-based app (Drupal) End-user must be able to do the following: • Create new 'media' content (if he/she is part of a user group that is allowed by the admins) • fill in the various fields • to upload multiple files (video, audio, image, text) and fill in the fields that are attached to the content type • to link a 'place/space' which is the geo-location (see fields of geo later) and define relation (home of, is about...)


• if there is not yet a geo-location then the user must be able to create one and return to the media and add the geo-location • to link user(s) and define their roles (this user is an interviewer, interviewee...) • if there is not yet a user then the user must be able to create one and return to the media and add the user • to link categories (this media belongs to the category 'interviews on Ground Zero) • if there is not yet a category then the user must be able to create one and return to the media and add the category • add keywords to the media which are pulled from a checkboxes as defined by mods • if the user does not find the appropriate keywords, then he/she can define new keywords which need to be approved (unless not as defined by the admin) by the admin. • be able to 'duplicate' a media-file and add a cue-in/cue-out for video and audio (if possible) • Create new geo-locations (if he/she is part of a user group that is allowed by the admins) • fill in the various fields • the user is able to load a (open street?) map OR to define exact coordinates which are then represented on a map • add a description to the geo-location • add multiple keywords for the geo-location using checkboxes, which are also categorized in topics (e.g. if the user does not find the appropriate keywords, then he/she can define new keywords which need to be approved unless not as defined by the admin) by the admin. • Create new categories (if he/she is part of a user group that is allowed by the admins) • fill in the various fields • link with other categories and define its relation (is child of, is parent of...) • add multiple keywords for the geo-location using checkboxes, which are also categorized in topics (e.g. if the user does not find the appropriate keywords, then he/she can define new keywords which need to be approved unless not as defined by the admin) by the admin. • Create new profiles • fill in the various fields • add specific predefined geo-locations and define role • Browse and search data BNA-BBOT Lakensestraat 119, 1000 Brussel, tel: 02/223.21.51 8 / 11 page(s)

• when searching using tags (auto-completed) the results should display the category, the geo-location, selection of users • browse the data based on all content-types and using filters • Browse a map and find all relevant data and filter for data • use a google map and GPS to find all stories that are around his/her current position • get a map with predefined maps of interesting walks • get a map with interesting spots to visit going from point A to point B • Define settings • choose language • define what can and cannot be seen of his/her profile

The moderators must be able to do the following • do all what the end-user can • block and unblock users • update/edit/unpublish/publish or delete content from all content types • approve or decline newly registered users • view and download data concerning • media and other data (views, downloads...) • visitors • traffic (referring websites...)

The admins must be able to do the following • do all what the end-user and mods do • update/edit or delete content from all content types • define the following settings • define the user permissions that (dis)allow


• specific groups to add data and this separately for media, geo-location, categories and users • specific groups to edit data • allow to create specific keywords • define whether newly submitted data must be published or reviewed • allow to change settings by mods • change labels of data (e.g. overrule the label 'category' and replace 'project' or 'topic') both for system-wide or group specific • Create, edit, delete users (except super admins) Super-admins must be able to • Do all what admins do • Create, edit, delete users (all) System must have • multi-language option • able to modify labels of data by super admin (as previously defined) • RDF output (or other metadata funct) 3.3.2 Browser-based app (CollectiveAccess) • System must have same functionality as Drupal (see previous) • must be decided whether the permissions must sync between Drupal and CollectiveAccess 3.3.3 Mobile App End-user must be able to: • Define the following settings: • define the data the user is interested in (based on categories defined by the admins) • work offline or online BNA-BBOT Lakensestraat 119, 1000 Brussel, tel: 02/223.21.51 10 / 11 page(s)

• Browse maps to • Browse a map and find all relevant data and filter for data • use a google map and GPS to find all stories that are around his/her current position • get a map with predefined maps of interesting walks • get a map with interesting spots to visit going from point A to point B

The system should update/sync • All data as stored in the content types (including deleted and modified data permissions of user roles and groups) 3.4 Other functionality The browser-based system must be able to: • be integrated with newsletters and mass-email functionality, using the emails of the profiles/users 4 Overige systemen Een korte lijst van systemen die momenteel verkend worden binnen BBOT: • MMBase • Adlib • Archon • Past Perfect • CALM • Cuadra • ...


Project MEE-KAARTEN. Beknopte beschrijving van het systeem & use case. Dirk Derom. t.a.v. Liesbeth Huybrechts

Recommend Documents