T3Gers: PLEASE REPLY BELOW, in prep for Feb T3G Third Thursday Webinar.
We will set up the Feb webinar to address issues, and will pre-invite some participants to share what they do. (Hopefully about 5 minutes apiece.)
Phil: Re Issue: Content people create is private (visible to the creator and admins only) until proactively shared with a group, the Org, or the public. Members in a group can be the only ones to view things. (Admins can always see everything.) Getting students comfortable making good metadata (and teachers comfortable requiring it) can help. "Everyone, make a tag for your item saying 'PH_Assig_20190214' so I can find them easily. If I have to go looking, you lose points for not having an important tag in place."
I came up with another "Issue": I have not been able to come up with a satisfying way for students to work collaboratively on a map or story map. One person/account has to be the owner and others cannot make changes to the owner's map or story map. This results in most group projects having one "map driver" with other students relegated to being content creators/collectors, which means they don't get the experience of editing the map or story map. And this is a real problem if the driver flakes out and leaves the group without a deliverable.
Sometimes students will attempt to get around this by sharing their login and password with their colleagues so they can all have editing access. This often results in the "too many cooks" scenario, where user A saves their work, thereby deleting user B's work that was previous saved but that user A had not added to their map/story map.
Our students regularly work on group projects using Google Apps, which seem to have figured out how to handle simultaneous editing. They don't understand why AGOL can't do the same.
Here are two resources that might be helpful for having multiple collaborators on a storymap.
Right! Choosing "Group members can update all group items" is very powerful ... but can also be a "good news, bad news" story if people are not careful. Sequence of operation is absolutely critical. To wit:
ArcGIS Online saves ONLY when the SAVE button is clicked. Because User3 opened the item before User2's changes were saved, the User2 changes are not in User3's map, and so will not exist when User3 saves. In this situation, Step3 needed to be done AFTER Step4.
Thanks, Charlie, that's EXACTLY my point. It's extremely difficult to explain that to students who are doing this for the first time and then similarly difficult for them to follow that protocol. This could really use a better solution in order for AGOL to become a better tool in a collaborative educational environment.
Understood Allen. It's not happening soon. The ArcGIS Online universe is the heart of a vast fleet of disparate tools, all of which need to work effectively together. The technology is built in a particular way, to meet the needs of uncountable types of users beyond students -- firemen on the go, foresters, coffee shop owners, airports, national defense departments, etc -- so while we always want to know what works or doesn't and what people want, sometimes the answer is "ok, that one not yet, so here's your best strategy." This is such a situation.
In my class, I am required to teach a CHYA curriculum for 2 weeks. Prior to this I started students on creating a StoryMap for the CalGeography StoryMap competition. I begin class by asking students if they are having difficulties, then I pick up with the CHYA curriculum. One student said that she created a subgroup for her and her partner. They were able to collaborate in that subgroup, but then couldn't upload their map to the Group that I set up. I am going to ask members of ArcGIS Online Geonet for some help in understanding this problem.
If they created a map and shared it into a group they control, the map can ALSO be shared into any other group they belong to. If you've made them members of a special group, and they can see that they are in the group (i.e. either you did not require them to accept an invitation, or you did require them to accept it and they did so), they just need to share the map again and check the box for that group.
Something that works well:
I use the homepage of the GRACE Project AGOO to advertise Esri's AGOO competition. The advertisement is a text announcement that links to a story map about the Michigan AGOO competition. The story map has a link to an entry submission form that I created with the survey123 web designer (no download needed). The resulting survey123 spreadsheet can be cut and pasted into the spreadsheet that the state submits to Esri. I used rules to shorten the survey if less than the maximum number of entries (5) are submitted. The locations, school names, and divisions of schools are also shown on a map in the story map.