Havenverse (a recreation of something that already exists)

http://docandersen.podbean.com

http://docandersen.spaces.live.com

I read recently about an idea similar to this in Technology Review.

A place of Safety

Havenverse

Value Statement: What if there was a single place where battered women, children terrified of their parents or guardians, people terrorized by their government or any other form of abuse could go to report that abuse and not have to worry about retaliation?

There are three considerations that will drive the creation and management of such a solution:

1. The security of the solution cannot be compromised in anyway

2. The anonymity of the user must be maintained regardless

3. The system will require human intervention to prevent spoofing and fake entries.

The first is critical and probably the single hardest thing to do in the short term computing world. Security from patches to worms and bots dominates the computing world of today. In the book Transitional Services I proposed a new way to consider security, the Aqueduct (keep the data moving along a series of connections and no one will ever know where the data actually is at any one time). I am not sure that would be an effective method for this system as the requirement here would be that the ID itself cannot be compromised.

Step two is difficult from two aspects. The first is the tracking of a user both on the local PC and on the web site they are connecting to. One of the components of the submission process has to be an intelligent around submissions. The submit button has to erase all history of that particular submission from the submission site, and the user’s PC or device.

Finally there has to be a built in ability for humans to intervene in cases of fraud or false claims. The number of claims will be fairly large so having ways to quickly reduce false submissions without losing any real claims will be critical.

.doc

Eduverse and Collaboration

http://docandersen.podbean.com

http://docandersen.spaces.live.com

Collaboration Design Requirements

· Ad hoc communication must be supported

· IM and VOIP steams must be integrated

· Web meetings and collaboration shares must be supported

· Late homework and assignment improvement tracking system

· Student project center

In the Ad-Hoc communication area of the Eduverse the following support has to be provided out of the box:

· Document sharing

· Workspace sharing

· Critique section

o Editors who are live to chat with students

o Experts with video’s and editing classes

· Youth forums (patrolled)

· Private Forums (patrolled)

· Web Meeting Section

· Chat section

· Student Project center

· Homework Help

The big areas here are to improve student’s collaboration skills, their understanding of editing and the editing process and encouraging the students to submit their materials to others for review. This provides a place for open and constructive communication and helps prepare the leaders of tomorrow with the tools of today.

Next there are the youth and private forums for discussions, these would be managed by topic and conversation (Science, Level 1, Introduction to science) while the Chat section would be completely open for children to converse about any and all topics.

.doc

Why “You sync” will fail and a possible solution

http://docandersen.podbean.com

http://docandersen.spaces.live.com

Why will “you sync” fail?

1. You miss a day – what did or didn’t you sync? What happens the next day, can you catch up putting the missing information in your Syncverse…

2. You miss a day, and lose hardware containing the only copy of the information which means that update will never happen

3. You forget to add something or were in a hurry

4. You forget you have something that required updating, now a day goes by is your update still relevant?

5. The upload failed (which you didn’t know) and no one got the update

Building an “auto sync” process for the Syncverse

All of these problems of course would “at times” impact an automated system unless, there was an operational model behind the overall solution. This would involve a three part process that would be managed both by users and by the system.

1. User gets a daily report on failed updates. They (the user) can then choose to force an update or notify their admin.

2. Administrator can set an auto retry on all updates. For home PC’s that the user may shut down, the system can force the update while the computer is appearing to be completely shut down (otherwise the user will power off the system).

3. The administrator gets a forwarded user report and forces an update.

This synchronization engine would also need some level of customization that can be controlled (otherwise every Monday morning the servers would be swamped).

· Site administrator assigns replication priority

· Replication is kicked off Sunday night (or the night before the work week starts if it is not Sunday)

· Incremental replication occurs at all times to always keep the site up to date.

The last option is the “easiest to managed” as you can create a delta replication concept (where the following formula can be leveraged):

Compare user timestamp to current time

This system would apply a timestamp to everything the user does, thus allowing for multiple time zones, multiple inputs and trickle replication. A significant delta in the timestamp to current time formula would allow the system to force an update to keep the data in the system fresh.

.doc

“You sync, I sync” we all sync for Ice Cream

http://docandersen.podbean.com

http://docandersen.spaces.live.com

What I sync:

What is it we are trying to organize? Are there data patterns and structures that would make this process easier?

What keeps all of this data fresh and up to date? Do you use the Armstrong computer system (a term my grandfather used to use to describe a pencil and paper? In this case it would be “YOU” syncing everything you have between all the various sources. If you leverage the “you sync” system there are bound to be errors or problems. Remember the day your power was out? You couldn’t log on? You drove to work thinking, I will sync everything when I get there. But your boss was waiting, a crisis in Puerto Rico required immediate attention. So you never synced. The next day you synced something’s you forgot but not everything. Now your system is out of alignment with no effective method of bringing it back to stasis. The “you sync” system has some flaws.

Can “you” be an effective engine?

1. Yes if all the information you sync is the same or if you make all the information generic enough that you can it in multiple locations but then are you actually leveraging a social network? I call this the cut copy and paste method but then the problem becomes do you use different systems for different groups of people.

a. WordPress has a feature where when I post my daily blog WordPress then notifies Twitter and Facebook automatically

b. I use a blog creation tool (windows live writer) that automatically notifies Twitter when I publish new blogs

2. If you spend a lot of time keeping everything up to date.

a. Facebook for personal status (friends)

i. Maintain existing social relationships

ii. Find old or lost friends

iii. Develop new relationships with people who have like interests.

b. My site for work status (work friends/co-workers)

c. Classmates or other social site focused on rediscovering old friends

Why will “you sync” fail?

1. You miss a day – what did or didn’t you sync?

2. You miss a day, and lose hardware containing the only copy of the information

3. You forget to add something

4. You forget you have something

.doc

More on the Eduverse

http://docandersen.podbean.com

http://docandersen.spaces.live.com

This section is in process

 

Collaboration Design Requirements

· Ad hoc communication must be supported

· IM and VOIP steams must be integrated

· Web meetings and collaboration shares must be supported

· Late homework and assignment improvement tracking system

· Student project center

In the Ad-Hoc communication area of the Eduverse the following support has to be provided out of the box:

· Document sharing

· Workspace sharing

· Critique section

o Editors who are live to chat with students

o Experts with video’s and editing classes

· Youth forums (patrolled)

· Private Forums (patrolled)

· Web Meeting Section

· Chat section

· Student Project center

The big areas here are to improve student’s collaboration skills, their understanding of editing and the editing process and encouraging the students to submit their materials to others for review. This provides a place for open and constructive communication and helps prepare the leaders of tomorrow with the tools of today.

 

,=.doc

Syncverse and Data Patterns

http:://docandersen.podbean.com

https://docandersen.wordpress.com

So what are the patterns within the data?

· My data (local)

o Things I need and use

o Is there a frequency or time requirement that makes this more effective stored locally?

· My data (remote)

o Items stored in various other locations – may be replicas “backups” of local data

o Items I created with a remote storage requirement (shared or collaborative documents, KM system etc.)

· My data (shared)

o In process

o Drafts

o Collaborative documents

· Free Public data (local, remote or shared)

o News feeds

o Information sources

o Media sources

· Managed Data (Information Merchants)

o News

o Reviews

o Analysts reports

o Media

o Help

o Guidance/best practices

· Government Data

o News

o Information

o Help

o Exposed Process

· Corporate data (local, remote or shared)

o Things I need to know

o Things I am working on

In my 2010 book Transitional Services I focused energy on the concept of push-pull data in consideration what would change over time for organizations as they moved to the cloud. That remains relevant – considering the data in a push format, a pull format or the combined push-pull format. Now we add the more cyclical components of data, its application and location.

.doc

UX considerations for the Eduverse

http://docandersen.podbean.com

http://docandersen.spaces.live.com

(please note this section is not complete)

Design UX considerations

A component of solution design is the concept of the user experience. There are a number of user populations that our solution will need to consider.

1. Teacher

2. Administrator

3. Student

4. Family

5. Government

Each of these interfaces will be slightly different overall. The teacher and student interfaces will be the tightest coupling and require the most change over time. Since the solution would be international

Student “level”

Interface Requirements

Notes

Level 1 – learning how to be a student

Simple, pictures rather than words, teacher controls the release of the word based interface as the students master learning.

Easiest interface – least number of choices. Parents would see a modified version of this for their screen.

Level 2 – learning the core skills of successful education

The interface slowly moves away from graphics to words. The screens get more complex over time managed by the teacher

Parents migrate to new screens with their children

Level 3 – mastering the core skills

Now the interface should be entirely words. If a language other than the native tongue is offered/taught the standard interface may change to only that language as the teacher judges it to be of value.

Parents interface begins to move away from a mirror interface and more to a monitoring interface

Level 4 – adding to the core skills

Now the interface may have additional options as the child may no longer be taking the classes from before (adding Photography, computer programing etc.)

Parents interface is wholly monitoring now.

we can’t use the European or US system of “grades” as they don’t always match. The Level’s described above would take us loosely into what we call Freshman/Sophomore year of High School. From there students being a much deeper specialization as they continue to expand and develop skills leveraging the core skills learn earlier in their school career. The important things with the initial user experience are as follows:

1. Student: starts simple and grows as their abilities grow. If a student struggles they can be easily taken back to the previous level. Students who advance faster than other students can be accommodated via this as well.

2. Teacher: see’s and chooses when students can advance their “home screens”

3. Parents: Initially model the child’s screens and eventually move to monitoring the child’s progress

4. Administrators (not listed in table above): See a comprehensive view of the school by teacher, level and by combinations of levels.

5. Government (not listed in table above): May be a level view by school, a view by school or even a view by geography – where geography could be a neighborhood, town or larger.

.doc