Here are some technical plans, Xenon sent me in a note card. The content below is slightly revised as result of a Skype meeting I had with her.
Word of caution. Note cards are not always correctly handled if recipient is off-line. This may be a particular risk if the system goes down in the meantime. Best route for blog members: post it as a separate post. If you put it in a comment, you need to send e-mail to the people you want to see it. Comments from blog members do not produce any notification to other people. I you post a new item, I will see it (via RSS) within a few hours.
Goals (If you don’t know your goals, you won’t know when you’ve won.)
Learners will be able to:
- copy an object (Take copy, as in that command)
- find the object in inventory (Find by search, using the name of the object)
- bring the object out of inventory (Rez the object)
- Open contents of the package object (Using open command, not edit)
- copy/move contents to inventory (Using relevant command after open)
- find objects copied/moved to inventory (with search, again)
- wear a wearable object (using wear command)
Objectives of video During the video, learners will:
- Observe the detailed user-system interactions for copying an object
- Observe the detailed user-system interactions for finding the object in inventory
- Observe the detailed user-system interactions for rezzing/bringing the object out of inventory
- Observe the detailed user-system interactions for opening contents of the package object
- Observe the detailed user-system interactions for copying/moving contents to inventory
- Observe the detailed user-system interactions for finding objects copied/moved to inventory
- Observe the detailed user-system interactions for wearing a wearable object
Notes. Observe is all we can say happened it the viewer watched the video. The expression detailed user-system interactions implies that we display a readable menu and illustrate the user action.
Concepts/Considerations/prerequisite skills:> What is inventory and how to view by search.
SE:
Open inventory is a prerequisite, but will be partly to thoroughly known by our prime audience. They met the operation during introduction. And they must bring with them (to SL) the more general concept of opening folder on the desk top. I favor brief mention of Inventory as folder and display of bottom bar with some action on the Inventory item.
> Concept of rezzing,
SE: Not clear what the concept is. Act of rez is in the objectives. Event will be in the vid. Once the object is rezzed, the relevant concept seems to be object rather than rez. Perhaps you mean conditions of rez, such as permissions and whether the system accepts your placement.
-
?? how to tell if you can rez an object by looking at the menu bar title (based on sim permissions)??
SE: I favor brief mention of restrictions as existing, no details. Advice to learner: If you get the EEGG at Hobo Village do you try-outs there. You can rez there and things will stay for a while.
> Moving v copying to inventory
SE: Need more detail. What is the distinction they need to understand?
> Mention no copy objects, show floating tab
SE: Can do as part of showing
Free to copy. designation.
> Differentiate between wear and attach - mention in this vid, maybe cover attach in a follow up vid.
SE: We will need to mention this distinction at the menu choice point. And say the words that delight all learners, “We’ll skip attach for now. You can find out about it later.”
Comment from SE: This section represents things we need to think about. How we handle them depends on whether they are parent skills (prerequisites), sibling skills (may be useful along with), or child skills (what you can learn them next).
Next steps: Task Analysis for objectives