University of Colorado
In attendance: Sylvia, Cecelia, Allyn, Luca, Jillian
************************* Joe's Comments **********************************
These comments are summarized from an earlier e-mail that I sent to Allyn and Ceceila regarding my experience using COG in an ad-hoc manner to help improve a workshop that I was involved in.
Suggestions (some obvious) about using COG in a workshop:
Agreed. There is already documentation that the users can view about using COG [http://earthsystemcog.org/projects/cog/tutorials] (Running the workshop)
Agreed. Part of the responsibilities of being a project lead/organizer ought to be to come up with an organizational plan. (Running the workshop)
Why? No single point of failure, but it is a resource constraint. Multiple developers not just project admins. Luca and Allyn are in charge of data, but most of the CoG folks could administrate. Luca is a bottleneck if he is not there to fix/change things. Need multiple people there to handle things.
TICKET: Develop project admin task protocols. (Sylvia)
Be sure to mention the person to contact when introducing the tool. (Running the workshop)
Glad to hear. (Running the workshop)
Glad to hear.
Every workshop will be different. But those that use ESGF to archive their data can have access to and services on that data integrated into COG. No way for an individual to upload stuff to the datanode. There is already an existing ticket on this, that we are just modifying. Best practices for where files should reside, or the size limit of the uploaded files. No limit that Luca is aware of at the moment. We do not want users to be using the CoG site to publish data, so perhaps we should put a limit on the uploadable file size. Set at the size of a large presentation document (100M).
We have discussed this since your email. I think that a formal template (as in "templated content") for this information is overkill, but we are working to make linking to documents/working with the wiki easier. We spent an entire call on this one point and there is already a ticket associated with it.
Agreed. I will ticket this. This is a problem of inconsistent nomenclature. The documents and attachments do not behave differently. Document can be limiting, although images are technically documents, the term is a little odd to apply to documents. Attachment is an odd term to use outside of the context of email. Change to “Add File”, which is more generic.
TICKET: change all instances of “add document/attachment” to “add file”.
I think that we are at the mercy of third-party tools here, but I will check with Luca. I do know that restricting search to project resources has been done. We have changed the wiki-tool being used here and that has changed the link search interface. We have also added the ability to restrict the search to the project.
TICKET: make sure this process is more user friendly
TICKET: add the project logo to the shared image library for that project.
There is a news feature. I believe that this is already ticketed, but I will double-check. This would be a nice feature, not sure if there is an existing ticket.
TICKET: News widget – enable email notification when news posted.
TICKET: News widget – enable tweeting when news posted.
TICKET: News widget – enable facebook pushes, where the user has the ability to post news items to facebook.
TICKET: News widget – enable google+ pushes, where the user has the ability to post news items to google+.
I think that this functionality already exists, but I will double-check. As for "drag and drop," I think that's very unlikely. We could make a topic called bookmarks in the left nav bar. Drag and drop is technically possible, but probably not worth our time/resources to implement. It is possible to change the parent of a subfolder.
TICKET: When adding a new bookmark, provide the ability to add a new folder.
TICKET: Remove the +add folder from the left nav.
TICKET: drag and drop functionality for bookmarks in the folders.
On facilitating group dynamics.
This is tricky, and the ideas here are a lot less thought-out. We (NCPP/Downscaling workshop) want to create workgroups that exist before the workshop and outlast the workshop. The groups would have potentially overlapping membership. On the other hand, I think it is unrealistic to expect the social cohesion and investment of time on the part of participants if the social network exists only for the duration of the workshop.
I am still impressed with what EarthCube did with their Ning site along these lines -- although I understand it had a lot of deficiencies for managing the larger EarthCube project. It was pretty basic and standard social-network stuff, but probably too much to add to COG. I think the essential parts of this is to have some sort of basic public COG profile information, picture/avatar, short bio, contact information. That can be (with opt-in) associated with many sub-projects. Having a way to spread email announcements to the sub-project. Having a more graphical way to display and navigate the sub-projects on the parent project site. I think that taking cues from existing social network sites and making the COG experience more intuitive for those who use these other sites would be a step in the right direction.
I don't know how much of this can be implemented within COG - you're asking a lot. But I will ticket it just so we have the request documented.
************* Luca will demo all the changes that went into release 0.9.7 *****************