Work plan: content model for the sharing platform 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) Type (Product / Service) Title Title Description Description Link to a product / service Link to a unit result Implementation site Impact focus areas Reference to impact focus area Collaborating country Reference to core function Milestone? (check) 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 taxonomy Project codes Project Code if applicable Execution Report Start Date End Date Responsible Staff Page, Blog post Wiki page Doc type taxonomy implementation report execution report meeting agenda meeting report success story presentation BTOR NSHR Implementation Report Author (default) Link to activity Date Authors Document Meeting Doc stage taxonomy working document formal reports internal published papers PERSON (USER) Author (default) Author (default) Link to activity Link to activity Date Start date, end date Authors People involved Type Stage Free tags applicable to all posts LOG activity View

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.

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