1 / 4

FAO OEKCS

FAO OEKCS. Work plan: content model for the sharing platform. FAO OEKCS WORKPLAN :: CONTENT MODEL FOR THE SHARING PLATFORM. OR-UR taxonomy Hierarchical e.g. H05 -- H0508. PRODUCT/SERVICE. ACTIVITY. CODE (computed: OR-UR-number). CODE (computed). Title. Type (Product / Service).

orestes-kristopher
Télécharger la présentation

FAO OEKCS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FAO OEKCS Work plan:content model for the sharing platform

  2. FAO OEKCS WORKPLAN :: CONTENT MODEL FOR THE SHARING PLATFORM OR-UR taxonomyHierarchicale.g. H05-- H0508 PRODUCT/SERVICE ACTIVITY CODE (computed: OR-UR-number) CODE (computed) Title Type (Product / Service) Description Title Description Link to a product / service Implementation site Link to a unit result Impact focus areas Collaborating country Reference to impact focus area Milestone? (check) Reference to core function Core functions Gender focused? (checkbox) Start Date Supports joint programming? (checkbox) End Date CCA, UNDAF codes Result of linking ongoing projects to workplan? (check) Areas identified in CCA, UNDAF (conditional) Responsible Staff NSHR POW taxonomyProject codes Project Code if applicable Execution Report Start Date End Date Responsible Staff Page, Blog postWiki page NSHR Doc type taxonomyimplementation reportexecution reportmeeting agendameeting reportsuccess storypresentationBTOR Implementation Report Author (default) Link to activity Date Authors Document Meeting Doc stage taxonomyworking document formal reports internalpublished papers PERSON (USER) Author (default) Author (default) Link to activity Link to activity Date Start date, end date Authors People involved Type Stage LOG activityView Free tagsapplicable to all posts

  3. Rules and Constraints The Hierarchy is OR-UR-P/S-At with strict one to many relation. Single posts (that are not OR, UR, P/S or At) can only refer to activities and each post can refer to one or more activities. Every P/S will have as the first default activity (code 00) an activity called General / Co-Ordination. Except for Wiki-nodes, all nodes can only by edited by the author and by the users to whom he gives permission (node_access). Since all nodes can have more than one author, views and statistics should consider the User reference repeatable fields (Responsible Staff, Authors, People involved) instead of the Drupal default author. Documents should be posted as Document nodes: the node body should contain the document text if possible, otherwise the document can be attached. Non-Document posts can have attachments, but only of external and non-core documents. If a post refers to a document, it has to link to the corresponding Document node.

  4. Useful Views Browse by all taxonomies Browse by all content types (P/S, activity, types of posts) Browse activities  Activity logs with filters and sorting options Browse users  User logs with filters and sorting options Communities around single P/S  or groups of P/S A hierarchy of PWB up to activity Level Tag Cloud (based on free tags) Personal Blogs Published Papers

More Related