Content and data structure
Data to be entered
Design areas
List from Jenny:
- Housing
- Water purification
- Water supply
- Sanitation
- Hygiene
- Solid waste management
- Organic waste management
- Transport
- ICT
- Food security
- Disaster management
For reference, the design areas have varied slightly in past years, but have included:
- Design area 1: Housing design & construction
- Design area 2: Water supply, sanitation and hygiene
- Design area 3: Energy
- Design area 4: Waste management
- Design area 5: Transportation
- Design area 6: Information communications technology
- Design area 7: Agriculture (for Pitchandikulum Forest)
- Or: Design area 7: Climate change (for Plan - Timor Leste)
- Design area 8: Sustainable Use of Biodiversity (for Kooma Traditional Owners Association)
- Design area 9: Eco-Tourism, Accommodation & Education Site (for Kooma Traditional Owners Association)
Questions & requests to EWB:
- Standardise spelling & capitalisation for categories etc. (Oxford spelling?) Transport or Transportation?
Questions to dev:
- Should EWB standardise the design areas, so they are the same from year to year? Or not a big issue?
Location
Current locations, TBC. (Others to be added in future years.)
- Tamil Nadu, India
- Ton Le Sap Lake, Cambodia
- Lautem district, Timor Leste
- The Gorkha District, Nepal
Year
Note for EWB: Make a clear definition of "year" for the project (e.g. due date of report submission). The academic year is different for institutions in the Northern and Southern hemispheres. The important thing is consistency, so a cohort's reports are grouped together.
Institutions
A list of the universities involved in Australia and New Zealand can be found at: http://www.ewbchallenge.org/content/students
A list of the universities in the UK and Ireland can be found at: http://www.ewbchallenge.org/students This list might change each year as more universities join.
Entry: Probably some kind of dropdown, possibly with AJAX (offering suggestions as you type).
University courses
This was taken off the list.
Question to EWB: Do we want to record this, just not as metadata?
Author/profile info
Probably not as metadata.
Contact info: Appropedia editors can be contacted by their profile page. This is preferable to making their email addresses public.
Note to dev: Users should be prompted to fill in appropriate information in their user profile, to ensure they can be contacted. This may include a reliable email address and/or social media contact.
Note to EWB: This message about being contactable should be given to students before signing up as well (or while assisting them in uploading their project info).
Appropedia:Status
Suggested by ~~: Appropedia:Status tags, showing the state of the technology. In essence, asking "How seriously should we take this report?"
The description page at Appropedia:Status describes:
- 2.1 Status:Design
- 2.2 Status:Model
- 2.3 Status:Prototype
- 2.4 Status:Verified
- 2.5 Status:Deployed
There should be a Status:Concept, but it hasn't been created yet.
Question to EWB: Include status tags? Prominently, near top?
Note to dev: Choose via dropdown?
Assessment
Question to EWB: Are there assessments or notes about the reports that should be described? E.g. a report may have an excellent analysis of the problem, but a particular proposed solution may be problematic.
Design brief and sample reports
Chriswaterguy (talk) has 3 documents to be shared with the semantic developer:
- "Plan TL EWB Challenge Project Design Brief" (design brief for participants in the Challenge, not for the web project)
- "2B Water Filtration Timor Leste" (sample report, of the kind which will be summarized for the semantic compendium on Appropedia)
- "4A_Water Purification Module" (another sample report)