Define project item IA

[jim]

Define a project item's IA.

1. start with very minimal, core, or slimline data item that can be expanded upon at a later date in the project and/or the user experience
2. work done to date by Jim as starting point: a 'slimline' or 'core' item: quick and easy to add, minimal detail as follows: - minimal amount of required information to minimise waffle and moderate-able info

• include some form of web standard vocabulary/ISO/something we can share with others (e.g. Project Dirt, Transition Drupal, GEN database, Wiser Earth)
• item status to represent 'approved', 'pre-approved', 'transition', 'other' project item statuses (see moderation points below)

[jim]

Content Types

A 'Project Submission' from the PSE may or may not the same as a Project Profile in the sense of data/content types on Transition Network. This because the latter is much more complex and has connections to many other parts of the system, while a PSE entry is deliberately simple. Indeed, it might be better to have a Project Submission as the initial state of a Project that is copied into the Project directory when accepted. This would keep the moderation queue and final content separate, and allow easier data entry/editing, moderation and display of submissions without risk of polluting the main Project directory. It also allows for a future where only some of the projects are imported into TN.org while others are suitable only for other sites. AND it helps keep this work separate from the core features of the TN site to avoid unnecessary coupling.

Essential fields

I'm currently working on the basis that a Project Submission is a separate content type that can 'accepted' during moderation and copied into the main TN Projects Directory.

Project fields to fill

• Title
• Project Aim (or description)
• Location (TBC: Map widget or Address block -- either way must return lat/long AND have a short, English version of the address)
• Project type (taxonomy term, ideally a select/drop down to broadly categorise the Project. Ideally related to Project Dirt, Transition Drupal, GEN database, Wiser Earth etc etc)
• Project website

Submission fields to fill

• Submitter Identifier (User ID, username OR just an email address -- depending on if we force registration to be part of submission)
• Submitter name (First & Last name)

Meta fields, auto-filled and hidden from user

• Post date
• Submission ID (almost certainly a node ID on target site)
• Status (set to 'pending' to begin)
• Source site ID (special ID representing the website the submission occurred on so we can map to webmaster user for notification and moderation purposes)
• Audience (could be 'transition', 'other' etc, auto filled or set by user?)

Nice to have fields

• Deeper Taxonomy term choices for better classification (as above, standard/shared vocabulary should be used
• 'More about this project' (a big fat text field, possibly with some pre-set titles in it as a writing aid.
• Project start date
• Project size (people involved)
• Stage (overlapping the TN Stages, but ideally a bit clearer than some of them ['deepening' vs 'building' gives me a semantic 'WTF?' moment)
• ... others from the ​Project Profile, or more sources?

[ed]

Ed has done a minor edit following our meet, and added it to the wiki here:
​https://wiki.transitionnetwork.org/Sharing_Engine/Project_Submission_IA#Content_Types

JK to own it and work it over

[jim]

Owned and worked... Will continue to tweak.

[jim]

Since for PSE alpha work the Project Profile content type changes need to be done, this is blocked by #384.

See ​https://wiki.transitionnetwork.org/Sharing_Engine/Project_Submission_IA -- we're mostly done pending merging the in ​https://wiki.transitionnetwork.org/Sharing_Engine/TN_Project_Form_Changes where appropriate.

[jim]

Believe #384 is done (Laura please close if so!)

PSE now done pending tweaks, closing.