Expedition Design Notes

Defining the data structure for expedition cards...how to think about this.

An expedition has an objective, and there are several prompting questions that correspond to Quests in an RPG.

• context: facility, cultural attraction, social attraction, individual need, SIG need
• activity type: building, locating, retrieving, researching, improving, maintaining, recruiting, practice/drill?
• form: what does the resulting concrete deliverable look like?
• form requirements: how do we check the concrete deliverable to make sure it meets our fitness requirements for its intended use?
• receiving: where does it go? who accepts it? (doesn't have to actually indicate use)

Let's just list the stuff out.

quest_listing_name: 'a short name to display'
quest_listing_desc: 'markdown text'
quest_owner: person_or_group
quest_info: { intent, expectation, motivation }
quest_beneficiary: { colony_context, person_or_group }
quest_text: 'markdown instructions for quest'
quest_type: building, locating, retrieving, researching, improving, maintaining, recruiting, practice/drill
quest_requirement: { [item]:{ desc, quantity, date, qualitative_text, form_description } }
quest_grantedby: person_or_group
quest_receivedby: person_or_group

JAVASCRIPT STUFF HERE

This is loading the stub script js/datastore.js