https://wiki.esipfed.org/w/api.php?action=feedcontributions&user=Kbene&feedformat=atomEarth Science Information Partners (ESIP) - User contributions [en]2024-03-19T08:06:23ZUser contributionsMediaWiki 1.35.14https://wiki.esipfed.org/w/index.php?title=K_Benedict_Statement&diff=65926K Benedict Statement2018-11-09T19:23:42Z<p>Kbene: </p>
<hr />
<div>''Back to [[Nomination_Committee/2019_Nominations_and_Ballot]]''<br />
<br />
I have enjoyed a long history with ESIP, starting at a representative to ESIP for the Earth Data Analysis Center in 2001, and through time chairing the IT&I Committee, serving as the Type III representative, Vice President, and President. I also served on the Foundation for Earth Science Board of Directors from 2010 to 2017 and served as President/Chair of the Board from 2012-2017. ESIP has a continuously supported and expanded the increased impact and use of Earth science data, and I have enjoyed and look forward to again leading ESIP in continuing this long tradition of effort.</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Data_Risk_Factors&diff=62633Data Risk Factors2017-10-18T17:42:27Z<p>Kbene: </p>
<hr />
<div>Data collections can face a variety of risk factors. This page provides a set of resources that will be used by members of the ESIP Data Stewardship Committee to analyze and categorize these factors. The goal of this activity is to inform and enable a) individuals and organizations who manage data collections, and b) individuals and organizations who are wanting to help to reduce the risks associated with data preservation and stewardship.<br />
<br />
<br />
==== LITERATURE ====<br />
<br />
Anderson, William L., Faundeen, John L., Greenberg, Jane, & Taylor, Fraser. (2011). Metadata for data rescue and data at risk. In Conference on Ensuring Long-Term Preservation in Adding Value to Scientific and Technical Data. http://hdl.handle.net/2152/20056<br />
<br />
Downs, Robert R. & Chen, Robert S. (2017). Curation of scientific data at risk of loss: Data rescue and dissemination. In Johnston, Lisa (Ed). Curating Research Data. Volume One, Practical Strategies for Your Digital Repository. Association of College and Research Libraries. http://dx.doi.org/10.7916/D8W09BMQ <br />
<br />
Griffin, R.E. (2015). When are old data new data? GeoResJ, 6: 92–97. http://dx.doi.org/10.1016/j.grj.2015.02.004<br />
<br />
Hsu, L., Lehnert, K.A., Goodwillie, A., Delano, J.W., Gill, J.B., Tivey, M.A., Ferrini, V.L., Carbotte, S.M., Arko R.A. (2015). Rescue of long-tail data from the ocean bottom to the Moon: IEDA Data Rescue Mini-Awards, GeoResJ, 6:108-114, http://dx.doi.org/10.1016/j.grj.2015.02.012. <br />
<br />
Ryan, H. (2014). Occam’s razor and file format endangerment factors. Proceedings of the 11th International Conference on Digital Preservation (iPres), October 6-10, 2014: Melbourne, Australia (pp. 179-188). https://www.nla.gov.au/sites/default/files/ipres2014-proceedings-version_1.pdf<br />
<br />
Thompson, C.A., Robertson, W. D., & Greenberg, J. (2014). Where have all the scientific data gone? LIS perspective on the data-at-risk predicament. College & Research Libraries, 75(6), 842-861. https://doi.org/10.5860/crl.75.6.842 <br />
<br />
Michener, William K., et al. “Nongeospatial Metadata for the Ecological Sciences.” Ecological Applications, vol. 7, no. 1, Feb. 1997, pp. 330–42. Wiley Online Library, doi:10.1890/1051-0761(1997)007[0330:NMFTES]2.0.CO;2. [http://onlinelibrary.wiley.com/doi/10.1890/1051-0761(1997)007[0330:NMFTES]2.0.CO;2/abstract]<br />
<br />
<br />
==== ORGANIZATIONS & GUIDELINES ====<br />
Guidelines to the Rescue of Data At Risk, https://www.rd-alliance.org/guidelines-rescue-data-risk <br />
<br />
Research Data Alliance Data Rescue Interest Group. https://www.rd-alliance.org/groups/data-rescue.html<br />
<br />
US Geological Survey. 2016 Data at Risk Project. https://www.fort.usgs.gov/ldi/2016-data-at-risk-project <br />
<br />
National Oceanic and Atmospheric Administration. Climate Database Modernization Program. https://www.ncdc.noaa.gov/climate-information/research-programs/climate-database-modernization-program<br />
<br />
International Environmental Data Rescue Organization (IEDRO), http://iedro.org/<br />
<br />
Tan, L. S., S. Burton, R. Crouthamel, A. van Engelen, R. Hutchinson, L. Nicodemus, T. C. Peterson, F. Rahimzadeh. (2004). Guidelines on Climate Data Rescue. WMO/TD No. 1210. Ed. by P. Llansó and H. Kontongomde. Geneva, Switzerland: World Meteorological Organization. http://www.wmo.int/pages/prog/wcp/wcdmp/documents/WCDMP-55.pdf<br />
<br />
<br />
==== CODATA/RDA 2016 WORKSHOP ====<br />
<br />
The Rescue of Data At Risk: An RDA / CODATA Workshop<br />
http://www.codata.org/task-groups/data-at-risk/dar-workshops<br />
<br />
Agenda - http://www.codata.org/uploads/RescueofDataatRisk-WorkshopAgenda.pdf<br />
<br />
Videos<br />
* Session 1 - https://www.youtube.com/watch?v=cE5CDaIytZI<br />
* Session 2 - https://www.youtube.com/watch?v=OgHH9-vuFsw<br />
* Session 3 - https://www.youtube.com/watch?v=NihiszNms3o<br />
* Session 4 - https://www.youtube.com/watch?v=i6q91LFJ7aU<br />
* Session 5 - https://www.youtube.com/watch?v=ePp2JOdHrJQ<br />
<br />
Presentation slides - https://drive.google.com/drive/folders/0B_NJP_ik1Aj-M0Z5aG1tSFNDVmM?usp=sharing<br />
<br />
<br />
==== TRUSTED DATA REPOSITORY CERTIFICATIONS ====<br />
<br />
Center for Research Libraries and Online Computer Library Center, Inc. (2007). Trustworthy Repositories Audit & Certification: Criteria and Checklist. https://www.crl.edu/archiving-preservation/digital-archives/metrics-assessing-and-certifying/iso16363<br />
<br />
Data Preservation Sub-Committee of the USGS Fundamental Science Practices<br />
Advisory Committee (FSPAC). (2015). FSPAC Data Preservation Criteria for a Trusted Digital Repository. https://docs.google.com/spreadsheets/d/1DQ3XDRoe7THmoFxwPoV2lcEqkn0Q7SkrPQfizxm6fLU/edit#gid=1446608780<br />
<br />
Data Seal of Approval and ICSU World Data System. (2016). Core Trustworthy Data Repositories Requirements. https://drive.google.com/file/d/0B4qnUFYMgSc-eDRSTE53bDUwd28/view<br />
<br />
McGovern, N. Y. (2016). DPM “Stack”: A Management Infrastructure Frame for Digital Preservation that Parallels Technical Infrastructure. <br />
https://www.dataone.org/sites/default/files/sites/all/documents/dws13dec2016.pdf<br />
<br />
Nestor Certification Working Group. (2013). Explanatory Notes on the Nestor Seal for Trustworthy Digital Archives. http://d-nb.info/1047613859/34<br />
<br />
Peng, G. (2015). The scientific data stewardship maturity assessment model template. Version: NCDC-CICS-SMM-0001-Rev.1 v4.0 06/23/2015. https://dx.doi.org/10.6084/m9.figshare.1211954<br />
<br />
Rans, J. and Whyte, A. (2017). Using RISE: the Research Infrastructure Self-Evaluation Framework. http://www.dcc.ac.uk/resources/how-guides/RISE<br />
<br />
Stall, S. (2016, December). So You want to Be Trustworthy: A repository’s Guide to Taking Reasonable Steps Towards Achieving ISO16363 . Poster presented at the 2016 AGU Fall Meeting, San Francisco, CA.<br />
<br />
<br />
==== COMMITTEE MEMBER EXPERIENCE ====<br />
<br />
Ramapriyan, H.K. 2017. NASA's EOSDIS, Trust and Certification. Presented at 2017 ESIP Summer Meeting, Bloomington, IN. <br />
https://figshare.com/articles/NASA_s_EOSDIS_Trust_and_Certification/5258047</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Carol_Meyer_Trading_Card&diff=46123Carol Meyer Trading Card2014-03-31T20:57:52Z<p>Kbene: /* Thanks to Carol */</p>
<hr />
<div>Like we have done for past ESIP president's, we've created a trading card for Carol. Please 'sign the card' by [http://wiki.esipfed.org/index.php?title=Carol_Meyer_Trading_Card&action=edit&section=1 editing the wiki page] below. *<br><br />
<br />
[[Image: ESIP Baseball Card FRONT Carol lg.png|400px]]<br />
[[File:ESIP Baseball Card BACK Carol lg.png|400 px]] <br> <br />
<small><nowiki>*</nowiki> Thank you to Kevin Ward, NASA Earth Observatory, for supplying the background patchwork image, see the [http://nasaesw.strategies.org/interactive/ digital, interactive version here]. </small><br />
<br />
Carol has been with the Foundation Foundation for Earth Science, the secretariat for ESIP, since 2003 and served as the Foundation's Executive Director since 2008. During this time she's championed the ESIP Federation, supported the growth of the ESIP membership to over 150 organizations and has helped raise the visibility and importance of Earth science data and informatics. One of her sayings is 'Let ESIP be ESIP' - this phrase captures the essence of ESIP's community-led nature and because of that flexibility and openness. ESIP has thrived under her watch. <br />
<br />
Carol learned to drive in NYC and NJ and is an expert NYC driver. It is ESIP legend thatWhen the ESIP meeting was at Lamont, Carol drove part of a group fearlessly through NYC to a Yankees' game and drove home in pouring rain. Erin has also been in the car for at least a few u-turns because of their collective challenge navigating. <br />
<br />
In her free time for several summers, Carol played rec volleyball. Those skills came in handy at the Santa Barbara ESIP meeting.<br><br />
[[Image: CarolVolleyball.png]] [[Image: CarolVolleyball_2.jpg|150px]] <br><br />
<small>([https://www.flickr.com/photos/skolr/3701627650/in/set-72157621133449198/ Credit: Bruce Caron, more pics from this meeting])</small><br />
<br />
==Thanks to Carol ==<br />
* Carol, you have been a terrific boss and mentor. You've given me the room and support to grow and for that I'm grateful. I wish you all the best in this new role and am excited to see what comes next! - Erin Robinson<br />
* Thanks for everything you have achieved for ESIP. I am sure that you will spread success wherever you go and whatever you do. You will be missed. All the best with your new endeavor. - Emily Law<br />
* Carol, you made a difference, best wishes for your new endeavors. - Phil Yang<br />
* For more than a decade, Carol poured her enormous talent and energy into making ESIP what it has become. She welcomed new presidents and helped them shine. She made great meetings look easy. She is that person you’d always want to have on your team. We all wish her the best. She leaves ESIP a vibrant organization ready to move ahead with its mission. - Bruce Caron<br />
* Carol, thanks so much for helping build the federation. Wish you the best of everything with your future endeavors. - Ken Keiser<br />
* Carol, you have many wonderful gifts. One is the ability to motivate others to use their own gifts and find their place in the ESIP organization. Your unpretentious and engaging leadership encouraged us; you helped us find connections with each other and with important issues. You are a great friend and role model! - Christine White<br />
* Carol ! Thanks for all the great leadership and dedication to ESIP. All the best! - Ed Armstrong<br />
* Carol, You have been a real anchor, rudder, and sail, all in one, giving us stability, direction, and purpose. Thanks for faultlessly steering this ship on a solid course forward. You will be missed, but with new opportunities come prospects of making significant positive impacts. Keep making significant positive impacts. Good luck - Steve Kempler<br />
* Under the category of "always thinking ahead and always keeping the big picture in mind": Right after the January 2013 meeting, where Ann Bartuska referred me to Simon Liu, I visited with Simon about mutual interests and potential areas of collaboration. A week later, Carol emailed me that she'll be meeting with Simon soon and wanted to find out a bit about my projects with USDA. I told her about my visit with Simon, that I'd be happy to chat about my USDA projects, and that I'd love to see an ESIP group formed to focus on climate change and agriculture. Carol wrote back: "Wow, small world, eh? So, my interest is in connecting to USDA projects/people that are having difficulty using ESIP-member provided data. A Climate & Ag Cluster would be great! Do you want to chair? :)" So, "always thinking ahead and always keeping the big picture in mind" should be "always thinking ahead and always keeping the big picture in mind and never missing an opportunity." :) That was how the Agriculture and Climate Cluster began! Thanks, Carol, for all your help and encouragement. I wish you the best, always! - Bill Teng<br />
* Carol, I just want to tell you how much it means as a student to have someone as encouraging as you in our corner. I wish you the best with everything. - Reid Boehm<br />
* Carol, it has been great working with and around you for your entire 11-year tenure with the Foundation and Federation. Getting to know you and enjoy your combined sense of humor and focus on getting things done has made all of our work together fun and productive. While the version on the baseball card looks nice, I can't help but share the original photo from which the card version was derived - it is a great illustration of the things that make you smile.<br />
<br />
[[File:carolAndGnome.jpg|200px|thumb|left|Carol on the streets of Brussels, enjoying the scenery.]]<br />
<br />
* Carol, I almost can't imagine ESIP without you. Thanks for all the support and encouragement. Best wishes for your new endeavors! May the force be with you! - Ruth Duerr<br />
* Carol, best, best, best to you on your new endeavors. I'm sure you'll bring your special brand of collaboration to your next gig -- and here's hoping we can keep that brand alive with the next chapter of ESIP without you. Thanks for the modeling and inspiration! - Nancy Hoebelheinrich<br />
* Carol, best wishes of everything with your future endeavors. - Yuechen Chi</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=File:CarolAndGnome.jpg&diff=46122File:CarolAndGnome.jpg2014-03-31T20:55:52Z<p>Kbene: </p>
<hr />
<div></div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Carol_Meyer_Trading_Card&diff=46110Carol Meyer Trading Card2014-03-31T19:00:16Z<p>Kbene: /* Thanks to Carol */</p>
<hr />
<div>Like we have done for past ESIP president's, we've created a trading card for Carol. Please 'sign the card' by [http://wiki.esipfed.org/index.php?title=Carol_Meyer_Trading_Card&action=edit&section=1 editing the wiki page] below. *<br><br />
<br />
[[Image: ESIP Baseball Card FRONT Carol lg.png|400px]]<br />
[[File:ESIP Baseball Card BACK Carol lg.png|400 px]] <br> <br />
<small><nowiki>*</nowiki> Thank you to Kevin Ward, NASA Earth Observatory, for supplying the background patchwork image, see the [http://nasaesw.strategies.org/interactive/ digital, interactive version here]. </small><br />
<br />
Carol has been with the Foundation Foundation for Earth Science, the secretariat for ESIP, since 2003 and served as the Foundation's Executive Director since 2008. During this time she's championed the ESIP Federation, supported the growth of the ESIP membership to over 150 organizations and has helped raise the visibility and importance of Earth science data and informatics. One of her sayings is 'Let ESIP be ESIP' - this phrase captures the essence of ESIP's community-led nature and because of that flexibility and openness. ESIP has thrived under her watch. <br />
<br />
Carol learned to drive in NYC and NJ and is an expert NYC driver. It is ESIP legend thatWhen the ESIP meeting was at Lamont, Carol drove part of a group fearlessly through NYC to a Yankees' game and drove home in pouring rain. Erin has also been in the car for at least a few u-turns because of their collective challenge navigating. <br />
<br />
In her free time for several summers, Carol played rec volleyball. Those skills came in handy at the Santa Barbara ESIP meeting.<br><br />
[[Image: CarolVolleyball.png]] [[Image: CarolVolleyball_2.jpg|150px]] <br><br />
<small>([https://www.flickr.com/photos/skolr/3701627650/in/set-72157621133449198/ Credit: Bruce Caron, more pics from this meeting])</small><br />
<br />
==Thanks to Carol ==<br />
* Carol, you have been a terrific boss and mentor. You've given me the room and support to grow and for that I'm grateful. I wish you all the best in this new role and am excited to see what comes next! - Erin Robinson<br />
* Thanks for everything you have achieved for ESIP. I am sure that you will spread success wherever you go and whatever you do. You will be missed. All the best with your new endeavor. - Emily Law<br />
* Carol, you made a difference, best wishes for your new endeavors. - Phil Yang<br />
* For more than a decade, Carol poured her enormous talent and energy into making ESIP what it has become. She welcomed new presidents and helped them shine. She made great meetings look easy. She is that person you’d always want to have on your team. We all wish her the best. She leaves ESIP a vibrant organization ready to move ahead with its mission. - Bruce Caron<br />
* Carol, thanks so much for helping build the federation. Wish you the best of everything with your future endeavors. - Ken Keiser<br />
* Carol, you have many wonderful gifts. One is the ability to motivate others to use their own gifts and find their place in the ESIP organization. Your unpretentious and engaging leadership encouraged us; you helped us find connections with each other and with important issues. You are a great friend and role model! - Christine White<br />
* Carol ! Thanks for all the great leadership and dedication to ESIP. All the best! - Ed Armstrong<br />
* Carol, You have been a real anchor, rudder, and sail, all in one, giving us stability, direction, and purpose. Thanks for faultlessly steering this ship on a solid course forward. You will be missed, but with new opportunities come prospects of making significant positive impacts. Keep making significant positive impacts. Good luck - Steve Kempler<br />
* Under the category of "always thinking ahead and always keeping the big picture in mind": Right after the January 2013 meeting, where Ann Bartuska referred me to Simon Liu, I visited with Simon about mutual interests and potential areas of collaboration. A week later, Carol emailed me that she'll be meeting with Simon soon and wanted to find out a bit about my projects with USDA. I told her about my visit with Simon, that I'd be happy to chat about my USDA projects, and that I'd love to see an ESIP group formed to focus on climate change and agriculture. Carol wrote back: "Wow, small world, eh? So, my interest is in connecting to USDA projects/people that are having difficulty using ESIP-member provided data. A Climate & Ag Cluster would be great! Do you want to chair? :)" So, "always thinking ahead and always keeping the big picture in mind" should be "always thinking ahead and always keeping the big picture in mind and never missing an opportunity." :) That was how the Agriculture and Climate Cluster began! Thanks, Carol, for all your help and encouragement. I wish you the best, always! - Bill Teng<br />
* Carol, I just want to tell you how much it means as a student to have someone as encouraging as you in our corner. I wish you the best with everything. - Reid Boehm<br />
* Carol, it has been great working with and around you for your entire 11-year tenure with the Foundation and Federation. Getting to know you and enjoy your combined sense of humor and focus on getting things done ... (more in a bit)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Program_Committee&diff=42990Program Committee2013-03-14T17:38:55Z<p>Kbene: /* Future Agenda Topics */</p>
<hr />
<div>==Executive Committee of the ESIP Federation==<br />
<br />
===Members===<br />
*Karl Benedict, President<br />
*Annette Schloss, Vice President<br />
*Charles Hutchinson, Chair, Ficom<br />
*John Scialdone, Chair, Partnership<br />
*Chris Lenhardt, Chair, C&B<br />
*Brian Wee, Type I Rep<br />
*Emily Law, Type II Rep<br />
*Stefan Falke, Type III Rep<br />
*Curt Tilmes, Chair, Data Stewardship<br />
*Roberta Johnson, Chair, Education<br />
*Matt Austin, Chair, IT & I<br />
*Chris Mattmann, Chair, Products and Services<br />
<br />
===Activities===<br />
====Telecons====<br />
<br />
Next Telecon, March 14, 2013 at 2 EDT<br><br />
<br />
=====Agenda=====<br />
<br />
# Welcome and Introductions<br />
# Approval of [[Draft Excom Minutes| February minutes]]<br />
# Commons Governance Working Group Report ([http://commons.esipfed.org/node/1447 Governance Document])<br />
# Summer Planning ([[Summer 2013 Meeting|Planning Page]])<br />
# Committee Reports<br />
# Other Business<br />
<br />
=====Supporting Documents=====<br />
[[media:stateOfTheArt.doc | Draft State of the Art Template]]<br />
<br />
====Future Agenda Topics====<br />
*Revisit Award Criteria<br />
*Form Commons Governance Steering Committee<br />
<br />
====Minutes from recent telecons====<br />
[[Draft Excom Minutes]]<br><br />
[[Approved Excom Minutes]]<br><br />
<br />
===Working Groups and Clusters===<br />
There are currently no active workgroups. To view historic workgroups see: [[ExCom_Inactive_Workgroups|Inactive ExCom workgroups]]<br />
<br />
====Miscellaneous====<br />
[[Raskin Scholarship]]</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Program_Committee&diff=42989Program Committee2013-03-14T17:38:10Z<p>Kbene: /* Agenda */</p>
<hr />
<div>==Executive Committee of the ESIP Federation==<br />
<br />
===Members===<br />
*Karl Benedict, President<br />
*Annette Schloss, Vice President<br />
*Charles Hutchinson, Chair, Ficom<br />
*John Scialdone, Chair, Partnership<br />
*Chris Lenhardt, Chair, C&B<br />
*Brian Wee, Type I Rep<br />
*Emily Law, Type II Rep<br />
*Stefan Falke, Type III Rep<br />
*Curt Tilmes, Chair, Data Stewardship<br />
*Roberta Johnson, Chair, Education<br />
*Matt Austin, Chair, IT & I<br />
*Chris Mattmann, Chair, Products and Services<br />
<br />
===Activities===<br />
====Telecons====<br />
<br />
Next Telecon, March 14, 2013 at 2 EDT<br><br />
<br />
=====Agenda=====<br />
<br />
# Welcome and Introductions<br />
# Approval of [[Draft Excom Minutes| February minutes]]<br />
# Commons Governance Working Group Report ([http://commons.esipfed.org/node/1447 Governance Document])<br />
# Summer Planning ([[Summer 2013 Meeting|Planning Page]])<br />
# Committee Reports<br />
# Other Business<br />
<br />
=====Supporting Documents=====<br />
[[media:stateOfTheArt.doc | Draft State of the Art Template]]<br />
<br />
====Future Agenda Topics====<br />
Revisit Award Criteria<br />
<br />
====Minutes from recent telecons====<br />
[[Draft Excom Minutes]]<br><br />
[[Approved Excom Minutes]]<br><br />
<br />
===Working Groups and Clusters===<br />
There are currently no active workgroups. To view historic workgroups see: [[ExCom_Inactive_Workgroups|Inactive ExCom workgroups]]<br />
<br />
====Miscellaneous====<br />
[[Raskin Scholarship]]</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Summer_2013_Meeting&diff=42633Summer 2013 Meeting2013-02-11T17:31:19Z<p>Kbene: /* Earth Intelligence: Infographics Contest */</p>
<hr />
<div>===Dates===<br />
July 9-12, 2013<br />
<br />
===Venue===<br />
Friday Center at UNC Chapel Hill, North Carolina<br><br />
Afternoon at NC Museum of Natural Sciencees (http://naturalsciences.org)<br />
<br />
===Program===<br />
<br />
====Theme====<br />
*Disasters & Data/Information<br />
:*Data life cycle and disaster response<br />
:*Connecting to climate theme from winter meeting - taking data to action<br />
:*Bringing Data and Information to Action: Meeting needs on the ground in preparing for and response to disasters and extreme weather events<br />
:*Building the Value Chain for Earth Science Data and Information in Disaster Planning, Response and Management<br />
<br />
====Session Ideas====<br />
*Data sharing across agencies<br />
*Sea level rise (UNC, TheSeaMonster.net), John Bruno<br />
*Climate change impacts on cities (NYC), Cynthia Rosenzweig, NASA GISS<br />
<br />
====Known Activities/Sessions====<br />
<br />
*co-located DataONE User Working Group (July 7-8?)<br />
*July 10 afternoon at the Museum of Natural Sciences and Specialty Venue Format Requirements (baseline)<br />
:*[[Immersive Theater]]<br />
:*[[Daily Planet]]<br />
:*[[Broadcast]]<br />
*ISEES town hall<br />
<br />
====Action Items====<br />
*First timer follow up<br />
*IT&I Rant & Rave on Infographics (periscopic.com)<br />
*Possible approach: Prizes for best infographics, used to select some of museum presentations - disasters.<br />
<br />
==Earth Intelligence: Infographics Contest==<br />
Draft:<br />
<br />
In the Winter of 2013, the Federation announced the theme of moving from climate assessment, to intelligence and action.<br />
<br />
This move is signaled by a shift from earth data displays to earth data infographics and earth data public awareness and policy.<br />
<br />
To promote the development of earth data-rich infographics on the topic of understanding natural disasters through the use of earth data resources, the Federation is now proposing a contest for the best earth-data infographic about natural disasters.<br />
<br />
The goal of this contest is to encourage and support visualizations that enable the public to access earth science data and to realize how these data can help us understand natural disasters and our vulnerability to these.<br />
<br />
The contest will include two tracks: students and open. The student track is available to any student from high-school through university (and post-docs too). The open track is available to any submission, including corporations.<br />
<br />
Prizes: ????<br />
The winning infographic will be displayed at the ESIP Summer meeting and ????<br />
<br />
Deadlines:<br />
<br />
Rules: ???? [should be clear and specific]<br />
<br />
The submitted infographic must be original and not have been made public prior to this event.<br />
<br />
Can we do star ratings or other simplified ratings within the commons for combined star and comments for the infographics? Can we use these ratings in the balloting for the winners. This would give us a chance to exercise a commenting system in the Commons in addition to enabling the competition. <br />
<br />
The Foundation for Earth Science will receive a non-exclusive right to use all submissions. [[User:Bcaron|bruce c]] ([[User talk:Bcaron|talk]]) 12:13, 6 February 2013 (MST)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Summer_2013_Meeting&diff=42632Summer 2013 Meeting2013-02-11T17:30:47Z<p>Kbene: /* Earth Intelligence: Infographics Contest */</p>
<hr />
<div>===Dates===<br />
July 9-12, 2013<br />
<br />
===Venue===<br />
Friday Center at UNC Chapel Hill, North Carolina<br><br />
Afternoon at NC Museum of Natural Sciencees (http://naturalsciences.org)<br />
<br />
===Program===<br />
<br />
====Theme====<br />
*Disasters & Data/Information<br />
:*Data life cycle and disaster response<br />
:*Connecting to climate theme from winter meeting - taking data to action<br />
:*Bringing Data and Information to Action: Meeting needs on the ground in preparing for and response to disasters and extreme weather events<br />
:*Building the Value Chain for Earth Science Data and Information in Disaster Planning, Response and Management<br />
<br />
====Session Ideas====<br />
*Data sharing across agencies<br />
*Sea level rise (UNC, TheSeaMonster.net), John Bruno<br />
*Climate change impacts on cities (NYC), Cynthia Rosenzweig, NASA GISS<br />
<br />
====Known Activities/Sessions====<br />
<br />
*co-located DataONE User Working Group (July 7-8?)<br />
*July 10 afternoon at the Museum of Natural Sciences and Specialty Venue Format Requirements (baseline)<br />
:*[[Immersive Theater]]<br />
:*[[Daily Planet]]<br />
:*[[Broadcast]]<br />
*ISEES town hall<br />
<br />
====Action Items====<br />
*First timer follow up<br />
*IT&I Rant & Rave on Infographics (periscopic.com)<br />
*Possible approach: Prizes for best infographics, used to select some of museum presentations - disasters.<br />
<br />
==Earth Intelligence: Infographics Contest==<br />
Draft:<br />
<br />
In the Winter of 2013, the Federation announced the theme of moving from climate assessment, to intelligence and action.<br />
<br />
This move is signaled by a shift from earth data displays to earth data infographics and earth data public awareness and policy.<br />
<br />
To promote the development of earth data-rich infographics on the topic of understanding natural disasters through the use of earth data resources, the Federation is now proposing a contest for the best earth-data infographic about natural disasters.<br />
<br />
The goal of this contest is to encourage and support visualizations that enable the public to access earth science data and to realize how these data can help us understand natural disasters and our vulnerability to these.<br />
<br />
The contest will include two tracks: students and open. The student track is available to any student from high-school through university (and post-docs too). The open track is available to any submission, including corporations.<br />
<br />
Prizes: ????<br />
The winning infographic will be displayed at the ESIP Summer meeting and ????<br />
<br />
Deadlines:<br />
<br />
Rules: ???? [should be clear and specific]<br />
<br />
The submitted infographic must be original and not have been made public prior to this event.<br />
<br />
Can we do star ratings or other simplified ratings within the commons for combined star and comments for the infographics? Can we use these ratings in the balloting for the winners. This would give us a chance to exercise a commenting system in the Commons in addition to enabling the competition. <br />
<br />
The Foundation for Earth Science will receive a non-exclusive right to use all submissions. [[User:Bcaron|bruce c]] ([[User talk:Bcaron|talk]]) 12:13, 6 February 2013 (MST)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Summer_2013_Meeting&diff=42631Summer 2013 Meeting2013-02-11T17:28:51Z<p>Kbene: /* Action Items */</p>
<hr />
<div>===Dates===<br />
July 9-12, 2013<br />
<br />
===Venue===<br />
Friday Center at UNC Chapel Hill, North Carolina<br><br />
Afternoon at NC Museum of Natural Sciencees (http://naturalsciences.org)<br />
<br />
===Program===<br />
<br />
====Theme====<br />
*Disasters & Data/Information<br />
:*Data life cycle and disaster response<br />
:*Connecting to climate theme from winter meeting - taking data to action<br />
:*Bringing Data and Information to Action: Meeting needs on the ground in preparing for and response to disasters and extreme weather events<br />
:*Building the Value Chain for Earth Science Data and Information in Disaster Planning, Response and Management<br />
<br />
====Session Ideas====<br />
*Data sharing across agencies<br />
*Sea level rise (UNC, TheSeaMonster.net), John Bruno<br />
*Climate change impacts on cities (NYC), Cynthia Rosenzweig, NASA GISS<br />
<br />
====Known Activities/Sessions====<br />
<br />
*co-located DataONE User Working Group (July 7-8?)<br />
*July 10 afternoon at the Museum of Natural Sciences and Specialty Venue Format Requirements (baseline)<br />
:*[[Immersive Theater]]<br />
:*[[Daily Planet]]<br />
:*[[Broadcast]]<br />
*ISEES town hall<br />
<br />
====Action Items====<br />
*First timer follow up<br />
*IT&I Rant & Rave on Infographics (periscopic.com)<br />
*Possible approach: Prizes for best infographics, used to select some of museum presentations - disasters.<br />
<br />
==Earth Intelligence: Infographics Contest==<br />
Draft:<br />
<br />
In the Winter of 2013, the Federation announced the theme of moving from climate assessment, to intelligence and action.<br />
<br />
This move is signaled by a shift from earth data displays to earth data infographics and earth data public awareness and policy.<br />
<br />
To promote the development of earth data-rich infographics on the topic of understanding natural disasters through the use of earth data resources, the Federation is now proposing a contest for the best earth-data infographic about natural disasters.<br />
<br />
The goal of this contest is to encourage and support visualizations that enable the public to access earth science data and to realize how these data can help us understand natural disasters and our vulnerability to these.<br />
<br />
The contest will include two tracks: students and open. The student track is available to any student from high-school through university (and post-docs too). The open track is available to any submission, including corporations.<br />
<br />
Prizes: ????<br />
The winning infographic will be displayed at the ESIP Summer meeting and ????<br />
<br />
Deadlines:<br />
<br />
Rules: ???? [should be clear and specific]<br />
<br />
The submitted infographic must be original and not have been made public prior to this event.<br />
<br />
The Foundation for Earth Science will receive a non-exclusive right to use all submissions. [[User:Bcaron|bruce c]] ([[User talk:Bcaron|talk]]) 12:13, 6 February 2013 (MST)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Summer_2013_Meeting&diff=42630Summer 2013 Meeting2013-02-11T17:28:24Z<p>Kbene: /* Action Items */</p>
<hr />
<div>===Dates===<br />
July 9-12, 2013<br />
<br />
===Venue===<br />
Friday Center at UNC Chapel Hill, North Carolina<br><br />
Afternoon at NC Museum of Natural Sciencees (http://naturalsciences.org)<br />
<br />
===Program===<br />
<br />
====Theme====<br />
*Disasters & Data/Information<br />
:*Data life cycle and disaster response<br />
:*Connecting to climate theme from winter meeting - taking data to action<br />
:*Bringing Data and Information to Action: Meeting needs on the ground in preparing for and response to disasters and extreme weather events<br />
:*Building the Value Chain for Earth Science Data and Information in Disaster Planning, Response and Management<br />
<br />
====Session Ideas====<br />
*Data sharing across agencies<br />
*Sea level rise (UNC, TheSeaMonster.net), John Bruno<br />
*Climate change impacts on cities (NYC), Cynthia Rosenzweig, NASA GISS<br />
<br />
====Known Activities/Sessions====<br />
<br />
*co-located DataONE User Working Group (July 7-8?)<br />
*July 10 afternoon at the Museum of Natural Sciences and Specialty Venue Format Requirements (baseline)<br />
:*[[Immersive Theater]]<br />
:*[[Daily Planet]]<br />
:*[[Broadcast]]<br />
*ISEES town hall<br />
<br />
====Action Items====<br />
*First timer follow up<br />
*IT&I Rant & Rave on Infographics (periscopic.com)<br />
*Possible approach: Prizes for best infographics, used to select some of museum presentations - disasters. Can we do star ratings or other simplified ratings within the commons for combined star and comments for the infographics?<br />
<br />
==Earth Intelligence: Infographics Contest==<br />
Draft:<br />
<br />
In the Winter of 2013, the Federation announced the theme of moving from climate assessment, to intelligence and action.<br />
<br />
This move is signaled by a shift from earth data displays to earth data infographics and earth data public awareness and policy.<br />
<br />
To promote the development of earth data-rich infographics on the topic of understanding natural disasters through the use of earth data resources, the Federation is now proposing a contest for the best earth-data infographic about natural disasters.<br />
<br />
The goal of this contest is to encourage and support visualizations that enable the public to access earth science data and to realize how these data can help us understand natural disasters and our vulnerability to these.<br />
<br />
The contest will include two tracks: students and open. The student track is available to any student from high-school through university (and post-docs too). The open track is available to any submission, including corporations.<br />
<br />
Prizes: ????<br />
The winning infographic will be displayed at the ESIP Summer meeting and ????<br />
<br />
Deadlines:<br />
<br />
Rules: ???? [should be clear and specific]<br />
<br />
The submitted infographic must be original and not have been made public prior to this event.<br />
<br />
The Foundation for Earth Science will receive a non-exclusive right to use all submissions. [[User:Bcaron|bruce c]] ([[User talk:Bcaron|talk]]) 12:13, 6 February 2013 (MST)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Summer_2013_Meeting&diff=42629Summer 2013 Meeting2013-02-11T17:26:09Z<p>Kbene: /* Theme */</p>
<hr />
<div>===Dates===<br />
July 9-12, 2013<br />
<br />
===Venue===<br />
Friday Center at UNC Chapel Hill, North Carolina<br><br />
Afternoon at NC Museum of Natural Sciencees (http://naturalsciences.org)<br />
<br />
===Program===<br />
<br />
====Theme====<br />
*Disasters & Data/Information<br />
:*Data life cycle and disaster response<br />
:*Connecting to climate theme from winter meeting - taking data to action<br />
:*Bringing Data and Information to Action: Meeting needs on the ground in preparing for and response to disasters and extreme weather events<br />
:*Building the Value Chain for Earth Science Data and Information in Disaster Planning, Response and Management<br />
<br />
====Session Ideas====<br />
*Data sharing across agencies<br />
*Sea level rise (UNC, TheSeaMonster.net), John Bruno<br />
*Climate change impacts on cities (NYC), Cynthia Rosenzweig, NASA GISS<br />
<br />
====Known Activities/Sessions====<br />
<br />
*co-located DataONE User Working Group (July 7-8?)<br />
*July 10 afternoon at the Museum of Natural Sciences and Specialty Venue Format Requirements (baseline)<br />
:*[[Immersive Theater]]<br />
:*[[Daily Planet]]<br />
:*[[Broadcast]]<br />
*ISEES town hall<br />
<br />
====Action Items====<br />
*First timer follow up<br />
*IT&I Rant & Rave on Infographics (periscopic.com)<br />
*Possible approach: Prizes for best infographics, used to select some of museum presentations - disasters<br />
<br />
==Earth Intelligence: Infographics Contest==<br />
Draft:<br />
<br />
In the Winter of 2013, the Federation announced the theme of moving from climate assessment, to intelligence and action.<br />
<br />
This move is signaled by a shift from earth data displays to earth data infographics and earth data public awareness and policy.<br />
<br />
To promote the development of earth data-rich infographics on the topic of understanding natural disasters through the use of earth data resources, the Federation is now proposing a contest for the best earth-data infographic about natural disasters.<br />
<br />
The goal of this contest is to encourage and support visualizations that enable the public to access earth science data and to realize how these data can help us understand natural disasters and our vulnerability to these.<br />
<br />
The contest will include two tracks: students and open. The student track is available to any student from high-school through university (and post-docs too). The open track is available to any submission, including corporations.<br />
<br />
Prizes: ????<br />
The winning infographic will be displayed at the ESIP Summer meeting and ????<br />
<br />
Deadlines:<br />
<br />
Rules: ???? [should be clear and specific]<br />
<br />
The submitted infographic must be original and not have been made public prior to this event.<br />
<br />
The Foundation for Earth Science will receive a non-exclusive right to use all submissions. [[User:Bcaron|bruce c]] ([[User talk:Bcaron|talk]]) 12:13, 6 February 2013 (MST)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41510Commons Steering Committee Workspace2012-10-19T15:18:22Z<p>Kbene: </p>
<hr />
<div>= Working Document =<br />
Governance working group - please claim a section of the linked document and begin filling it in based upon our discussions and the notes that we have compiled here and in our meeting minutes. <br />
<br />
Link to the working Google Doc (only working group members can access this document):<br />
https://docs.google.com/document/d/1ZKY6zDRPpIKGHtOJC987nXjuBvJOtQhDQyKQDnyn4mQ/edit<br />
<br />
= Next Working Group Call = <br />
Friday, November 2<br />
11:00 am MDT<br />
<br />
WebEx connection info (same as previous calls) will be sent out in the days before the meeting. <br />
<br />
= Notes =<br />
<br />
== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
==Draft Vision Statement==<br />
<br />
=== Current draft language ===<br />
<br />
The ESIP Commons will be the central destination for the Earth Science community to access and interact with the knowledge of the ESIP Federation<br />
<br />
=== previous ===<br />
The ESIP Commons will be a valued participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
<br><br />
<br />
===Alternative draft language===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science?<br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
* Need to give ESIP Commons permission to republish while author's retain copyright - this would not be needed if CC or Public Domain are the only choices. <br />
* Creative Commons as a "preferred" option for materials posted through the Commons? Public domain? Also CC0?<br />
* Author certification of copyright<br />
* Enable a botton for all content to flag potential copyright violations/issues?<br />
* DMCA process?<br />
* Blanket license for submitted comments, agreed to during account creation process.<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
* Dispute resolution<br />
* Management of overall Commons "structure" - categories, sections, etc.<br />
* Development (with content area editors) of a Commons ''Style Guide''<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
* Style Guide - including license info embedded in document<br />
<br />
== Resources ==<br />
<br />
[http://www.lulu.com/us/en/about/member-agreement Lulu Member Agreement]<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Commons Governance minutes for October 12, 2012 1pm EST<br />
Attendees: Karl, Erin, Kevin, Bob, Reid<br />
<br />
Karl shared Google docs document: Principles and Policies<br />
Dimensions of Commons governance issues that needed to consider<br />
• Mission & vision attributes<br />
• Dimensions of licensing options related to the commons<br />
• Principles and policies as outcome of discussions <br />
• Roles of steering committee<br />
Members take on writing role of outline- definition of the governance guiding principles and policies.<br />
<br />
Karl- start to translating the discussion to language of policy for contributors- what might be structure of management for Commons?<br />
• Key- question of licensing: having a cc style as a default and as a preferred license<br />
Bob- agrees would say to go with the cc by license (attribution license)<br />
Karl; need or desire for gov. members to have a public domain license option?<br />
Kevin- yes- not sure from NASA what is the desired type<br />
Bob- cc by license assumes that you are owner and you have copywrite<br />
• once you are the holder than you can assign the cc license to it. working for a gov agency- depending on how create- dictate what your options are<br />
• do the work at your office- at the agency- considered public domain<br />
• if on your own time- own resources- wouldn't fall under that agency<br />
<br />
Karl- we could have material that is public domain that agency- putting content and propagating that state into the commons- otherwise the copyright is owned by the person and they can certify it as such.<br />
<br />
Bob- if possible # of license for options should limited it might be confusing - be careful to not have too many but public domain offer is good for gov and others who would decide<br />
<br />
Karl- pub domain concern because it doesn't have the attribution so not as preferred <br />
Bob- need for people to know what getting into<br />
<br />
Kevin<br />
• maybe have a webex to explain copyright types - have an expert<br />
• from visualization cluster- presenters and presentation only one license applicable for whole wasn't a way to assign license to different <br />
Erin- presentations should have its own content type- working on that process<br />
<br />
Bob- cc by-license badge cut and paste into document- recognizable can even put explanation and url so can read if need to.<br />
<br />
Karl- may want to build that in- don't have in the wiki page or in the document outline-<br />
• style guide for content- good element for style guide<br />
• explicit embedding of the license into the document not just in the metadata- standard of practice<br />
-Adding a section for the style guide-<br />
• simplicity of the cc -by<br />
• many journals (open access- use the cc by license) pretty much standard<br />
• Karl- would that cause any time where work against us?<br />
• Goal is max. share-ability and usability while maximizing amount can get in<br />
• Karl- how about also the cc 0 - more international compliance or understanding of public domain<br />
• Bob- other issues have occurred- legal arguments<br />
<br />
Another area- core for documentation: definition of the roles and responsibilities for the different actors<br />
• Model- who are the actors in the commons?<br />
• How do we define the roles and responsibilities<br />
• Created 4 different actors (plus one)<br />
1. steering comm<br />
2. content area editors<br />
3. content contributors<br />
4. content administrators<br />
5. Users (contributing in the form of comments)<br />
• Licensing- for comments- Users must be registered with the system in order to comment gives us an opportunity to have users agree that their comments will fall under a particular license<br />
• We could look at cc-by license for commons proper to keep simple<br />
• Do commenters own comments?<br />
• Available under a cc- by license, commenters still own (we provide attribute) post same comments elsewhere<br />
<br />
• Bob- giving opportunity to contribute that they understand that you can't be held liable- can delete and revise as needed <br />
• Karl- brings back to the roles and responsibilities for the system orchestrator<br />
<br />
• Contributors: developing content- need to certify that they own the cc and allowed to contribute need to follow regulations according to the guide<br />
<br />
• Bob provides scenario: say contributor put up content in good faith- user has privileges to make comment that is nasty: accuse author- author disappears but accusation remains- could be detrimental to the reputation of the person who has posted it- like graffiti<br />
<br />
• Erin- policy on the site for constructive comments only<br />
<br />
• Karl- that is what the function of content area editors would regulate- deciding the content areas by specific constraints- designated editor or editors- they would be a set of eyes before publication<br />
• set of standards across the commons as a whole-- style guide<br />
• essentially community standards- editors flip the switch<br />
• would lean more towards removal rather than editing<br />
• troll-like comments- community norm- vigorous debate- we could have areas designed for vigorous conversation<br />
• kind of a sand box area<br />
• Understanding that there may be norms in different areas <br />
• Bob- another way that can help facilitate growing content would be to have the capability to flag the content send an email <br />
• Kevin- self-policing kind of like on youTube<br />
• Karl- Erin- can we do that?<br />
• E- not native- probably can find a module<br />
<br />
• Karl- may be editorial or content level decisions that may get appealed controversy- court of last resort is the steering committee itself could bring appeals to the steering committee for final adjudication<br />
<br />
• Bob- individuals serving for area editors-removing content- authors of that content - may lash out at the editors. Anonymity of content area editors? Not make explicit who is regulating<br />
<br />
• Erin- anonymous review is good idea- may be making issues for ourselves light touch <br />
• Karl- core goals- high degree of transparency- including on who is providing the community policing- we would deal with any trolls visibly and publicly<br />
• Bob- what if he works for the funding agency and the editor feels in jeopardy<br />
• Erin- I think we would need to just cross that bridge when we get there <br />
• Karl- be prepared to work through scenarios as they arise work through our mechanisms in place- local decision making- but can intervene<br />
Karl asks- Is it time to start writing sections of document- one more week?<br />
Erin- start to write this week -issues will be flushed out<br />
Email or in Google doc just put name out on section heading<br />
<br />
Meeting next week (same time): Friday October 19, 2012 1pm EST.<br />
<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:14, 12 October 2012 (MDT)<br />
<br />
<br />
<br />
<br />
Commons Governance minutes for October 5, 2012 2pm est.<br />
Attendees: Karl, Carol, Chris, Reid<br />
Some technical difficulties with Webex: <br />
Accessed ability to share screen through Karl’s “Go to Meeting” account and through the Web ex phone line.<br />
<br />
Talking through vision statement<br />
• Vision statement in future tense<br />
• Participatory- build in that thought later<br />
• more than a publishing<br />
• aggregator- work space for the community interactive<br />
• go back to looking at the mission<br />
• core or central destination for the earth science community to access the knowledge of the ESIP Federation<br />
• Karl- and interact with<br />
revisit it move on to licensing…<br />
and role of the steering committee…<br />
<br />
Licensing: assignment of permission to publish the contact<br />
• License assigned to the material may not be the absolute requirement<br />
• Creative commons by-license- don't have to have permission to republish from creator<br />
• Lulu: contributors keep the copyright but give permission<br />
• Community generated content. …Different than content such as posters<br />
• ESIP ability to use -license doesn't mean you give up the right to it<br />
• Karl: How do you think folks would feel about that- partners who are publishing materials- would this cause them heartache?<br />
• Carol: what about presentations?<br />
• Government agencies- might have some roadblocks <br />
• Don’t want to have a requirement for publishing in the commons- barriers to some presenters<br />
• Making it optional for people…. creative/commons or public domain as another option<br />
• Karl to Chris- any experiences <br />
• Public domain as another option would not complicate<br />
• Creative commons has a public domain definition/ option (?)<br />
• Carol: Can we have a series of checkboxes to denote individual agency on making decisions<br />
• Couple of things that folks would need to do licenses to choose from- also need them to certify that they have the right to do this that they are the copyright owner<br />
• Understand their content- must license those previous-exceeding limits of license copies<br />
• Through the combination of the certification and the choice of license that is available to them we provide the citation information to them and cover ourselves - due diligence with submitted content<br />
• Capability for each piece of content to identify or flag possible copyright issues- how to handle that- <br />
*You Tube changing their model to non-digital millennium copyright- poster could repeal you tube defined process them now changing over to a process through the dmca notify who they think the copy write owners - issue formal "take-down request" simplifies through legal process through dmca process *<br />
• previous discussion about licensing-- wiki is by default is the gnu free documentation license- by understanding gnu fdl is assigned<br />
• Chris- then license is different- content is different than the wiki<br />
• Karl yes- given that the content and submission styles are sufficiently different- also materials going in are further along in the spectrum- more "static publications" <br />
• ie: white page in the commons choose one of the creative commons we have available- then we also have a comment space where we are explicitly submitting (we need a blanket copyright)<br />
• account creation: agreement comments created in the commons are subject to license x<br />
• can choose for submitted content but not comments<br />
• move away from creative commons being only option but may move more toward public domain<br />
• have the creative commons to be the preferred license- may have a reason for submitting as public domain (try to discourage) but still beneficial in terms of knowledge sharing <br />
• creative commons has a public domain<br />
• Carol: a preferred approach- that can be the default check and then give the other options <br />
• also cc- zero "wave all the interests slightly different than complete public domain<br />
• examples of policies: flicker ( like the language and readability) also plos<br />
• take one of these wiki categories that we pulled out highlight bullets that we want to see in a policy<br />
• take a stab at developing an outline borrow pretty liberally with attribution of course<br />
• Karl-outline for policy document based<br />
'''<br />
Meet next week an hour earlier 1pm EST next Friday, October 12, 2012 <br />
'''<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:55, 5 October 2012 (MDT)<br />
<br />
<br />
Commons Governance minutes for September 21, 2012 2pm est.<br />
Attendees: Karl, Carol, Chris, Rahul, Reid<br />
Operational behavior of the Commons: content types/ area structures/ workshop materials<br />
how do we manage identifiers<br />
thoughts to the mission or vision<br />
Second half of the mission is almost there<br />
Attributes for how the commons will operate<br />
understanding that content is targeted towards broader audience<br />
permanent record it is not- but persistent record<br />
?tagging scheme<br />
browse-ability tags of access<br />
attribute additions- comment ability<br />
Carol- is this a descriptive tool or part of a vision statement<br />
Chris-Best Visions are short and sweet<br />
attributes are distilled down into brief and compelling<br />
Starting the wording for the vision statement<br />
capturing community knowledge through -the trusted leader in earth science information<br />
something short and direct for vision<br />
Vision: Karl- redefining the boundaries of publishing- doesn't match goal of ESIP separating the tech side from the out come of the Commons<br />
Carol: what is different about it- capturing knowledge that wouldn't otherwise be published grey literature-This is not business as usual- works in progress- <br />
ESIP Commons published the full breadth of knowledge generated by the ESIP community shared within the federation to advance earth science informatics<br />
K: Preserves and organizes: search, browse, ongoing discussion- capture of quality representing ongoing value of materials or knowledge/ Captures and organizes the breadth of knowledge<br />
Carol: shared? may not be the best word- sharing its knowledge<br />
community or breadth<br />
moving to google docs document:<br />
Rahul- is this as much a publishing arm- or … new documentation tool importance from research community- notion of publication<br />
Note for future (Reid-task) add to the list of governance- tagging member vs. non…<br />
we can tag member affiliation without stating member in vision<br />
how to reflect tagging and commenting ?social? not social<br />
Carol - we don't need the support of the informatics community<br />
In the mission we talk about the open, curated, sharing with thte broader community- Do that not just for the sake of the community, but to share with others<br />
Karl: Broad community of users…Meeting capture piece- discussion? is it in there?<br />
Rahul- it is enabled - we don't have control over whether people use it<br />
Carol: dynamic resource- changing content dynamic place, not just contributions but keeps the conversation going<br />
Rahul- systematically rather than organize- systematically applies and simplifies<br />
publishes the breadth of knowledge/ breath of content- diversity of content/ "diverse content contributed by" not supporting, but sharing<br />
content or knowledge- knowledge is not as broad- keeps the material broad<br />
Karl: copy and pasting into wiki: closing google document-<br />
current draft: The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
Next Meeting will be Friday October 5, 2012 at the same time 2pm EST.<br />
<br />
<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41431Commons Steering Committee Workspace2012-10-12T17:28:28Z<p>Kbene: /* Miscellaneous Discussion Items */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
==Draft Vision Statement==<br />
<br />
=== Current draft language ===<br />
<br />
The ESIP Commons will be the central destination for the Earth Science community to access and interact with the knowledge of the ESIP Federation<br />
<br />
=== previous ===<br />
The ESIP Commons will be a valued participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
<br><br />
<br />
===Alternative draft language===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science?<br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
* Need to give ESIP Commons permission to republish while author's retain copyright - this would not be needed if CC or Public Domain are the only choices. <br />
* Creative Commons as a "preferred" option for materials posted through the Commons? Public domain? Also CC0?<br />
* Author certification of copyright<br />
* Enable a botton for all content to flag potential copyright violations/issues?<br />
* DMCA process?<br />
* Blanket license for submitted comments, agreed to during account creation process.<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
* Dispute resolution<br />
* Management of overall Commons "structure" - categories, sections, etc.<br />
* Development (with content area editors) of a Commons ''Style Guide''<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
* Style Guide - including license info embedded in document<br />
<br />
== Resources ==<br />
<br />
[http://www.lulu.com/us/en/about/member-agreement Lulu Member Agreement]<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Commons Governance minutes for October 5, 2012 2pm est.<br />
Attendees: Karl, Carol, Chris, Reid<br />
Some technical difficulties with Webex: <br />
Accessed ability to share screen through Karl’s “Go to Meeting” account and through the Web ex phone line.<br />
<br />
Talking through vision statement<br />
• Vision statement in future tense<br />
• Participatory- build in that thought later<br />
• more than a publishing<br />
• aggregator- work space for the community interactive<br />
• go back to looking at the mission<br />
• core or central destination for the earth science community to access the knowledge of the ESIP Federation<br />
• Karl- and interact with<br />
revisit it move on to licensing…<br />
and role of the steering committee…<br />
<br />
Licensing: assignment of permission to publish the contact<br />
• License assigned to the material may not be the absolute requirement<br />
• Creative commons by-license- don't have to have permission to republish from creator<br />
• Lulu: contributors keep the copyright but give permission<br />
• Community generated content. …Different than content such as posters<br />
• ESIP ability to use -license doesn't mean you give up the right to it<br />
• Karl: How do you think folks would feel about that- partners who are publishing materials- would this cause them heartache?<br />
• Carol: what about presentations?<br />
• Government agencies- might have some roadblocks <br />
• Don’t want to have a requirement for publishing in the commons- barriers to some presenters<br />
• Making it optional for people…. creative/commons or public domain as another option<br />
• Karl to Chris- any experiences <br />
• Public domain as another option would not complicate<br />
• Creative commons has a public domain definition/ option (?)<br />
• Carol: Can we have a series of checkboxes to denote individual agency on making decisions<br />
• Couple of things that folks would need to do licenses to choose from- also need them to certify that they have the right to do this that they are the copyright owner<br />
• Understand their content- must license those previous-exceeding limits of license copies<br />
• Through the combination of the certification and the choice of license that is available to them we provide the citation information to them and cover ourselves - due diligence with submitted content<br />
• Capability for each piece of content to identify or flag possible copyright issues- how to handle that- <br />
*You Tube changing their model to non-digital millennium copyright- poster could repeal you tube defined process them now changing over to a process through the dmca notify who they think the copy write owners - issue formal "take-down request" simplifies through legal process through dmca process *<br />
• previous discussion about licensing-- wiki is by default is the gnu free documentation license- by understanding gnu fdl is assigned<br />
• Chris- then license is different- content is different than the wiki<br />
• Karl yes- given that the content and submission styles are sufficiently different- also materials going in are further along in the spectrum- more "static publications" <br />
• ie: white page in the commons choose one of the creative commons we have available- then we also have a comment space where we are explicitly submitting (we need a blanket copyright)<br />
• account creation: agreement comments created in the commons are subject to license x<br />
• can choose for submitted content but not comments<br />
• move away from creative commons being only option but may move more toward public domain<br />
• have the creative commons to be the preferred license- may have a reason for submitting as public domain (try to discourage) but still beneficial in terms of knowledge sharing <br />
• creative commons has a public domain<br />
• Carol: a preferred approach- that can be the default check and then give the other options <br />
• also cc- zero "wave all the interests slightly different than complete public domain<br />
• examples of policies: flicker ( like the language and readability) also plos<br />
• take one of these wiki categories that we pulled out highlight bullets that we want to see in a policy<br />
• take a stab at developing an outline borrow pretty liberally with attribution of course<br />
• Karl-outline for policy document based<br />
'''<br />
Meet next week an hour earlier 1pm EST next Friday, October 12, 2012 <br />
'''<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:55, 5 October 2012 (MDT)<br />
<br />
<br />
Commons Governance minutes for September 21, 2012 2pm est.<br />
Attendees: Karl, Carol, Chris, Rahul, Reid<br />
Operational behavior of the Commons: content types/ area structures/ workshop materials<br />
how do we manage identifiers<br />
thoughts to the mission or vision<br />
Second half of the mission is almost there<br />
Attributes for how the commons will operate<br />
understanding that content is targeted towards broader audience<br />
permanent record it is not- but persistent record<br />
?tagging scheme<br />
browse-ability tags of access<br />
attribute additions- comment ability<br />
Carol- is this a descriptive tool or part of a vision statement<br />
Chris-Best Visions are short and sweet<br />
attributes are distilled down into brief and compelling<br />
Starting the wording for the vision statement<br />
capturing community knowledge through -the trusted leader in earth science information<br />
something short and direct for vision<br />
Vision: Karl- redefining the boundaries of publishing- doesn't match goal of ESIP separating the tech side from the out come of the Commons<br />
Carol: what is different about it- capturing knowledge that wouldn't otherwise be published grey literature-This is not business as usual- works in progress- <br />
ESIP Commons published the full breadth of knowledge generated by the ESIP community shared within the federation to advance earth science informatics<br />
K: Preserves and organizes: search, browse, ongoing discussion- capture of quality representing ongoing value of materials or knowledge/ Captures and organizes the breadth of knowledge<br />
Carol: shared? may not be the best word- sharing its knowledge<br />
community or breadth<br />
moving to google docs document:<br />
Rahul- is this as much a publishing arm- or … new documentation tool importance from research community- notion of publication<br />
Note for future (Reid-task) add to the list of governance- tagging member vs. non…<br />
we can tag member affiliation without stating member in vision<br />
how to reflect tagging and commenting ?social? not social<br />
Carol - we don't need the support of the informatics community<br />
In the mission we talk about the open, curated, sharing with thte broader community- Do that not just for the sake of the community, but to share with others<br />
Karl: Broad community of users…Meeting capture piece- discussion? is it in there?<br />
Rahul- it is enabled - we don't have control over whether people use it<br />
Carol: dynamic resource- changing content dynamic place, not just contributions but keeps the conversation going<br />
Rahul- systematically rather than organize- systematically applies and simplifies<br />
publishes the breadth of knowledge/ breath of content- diversity of content/ "diverse content contributed by" not supporting, but sharing<br />
content or knowledge- knowledge is not as broad- keeps the material broad<br />
Karl: copy and pasting into wiki: closing google document-<br />
current draft: The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
Next Meeting will be Friday October 5, 2012 at the same time 2pm EST.<br />
<br />
<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41157Commons Steering Committee Workspace2012-10-05T18:59:29Z<p>Kbene: /* Licensing Options and Assignment of License to ESIP */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
==Draft Vision Statement==<br />
<br />
=== Current draft language ===<br />
<br />
The ESIP Commons will be the central destination for the Earth Science community to access and interact with the knowledge of the ESIP Federation<br />
<br />
=== previous ===<br />
The ESIP Commons will be a valued participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
<br><br />
<br />
===Alternative draft language===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science?<br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
* Need to give ESIP Commons permission to republish while author's retain copyright - this would not be needed if CC or Public Domain are the only choices. <br />
* Creative Commons as a "preferred" option for materials posted through the Commons? Public domain? Also CC0?<br />
* Author certification of copyright<br />
* Enable a botton for all content to flag potential copyright violations/issues?<br />
* DMCA process?<br />
* Blanket license for submitted comments, agreed to during account creation process.<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
* Dispute resolution<br />
* Management of overall Commons "structure" - categories, sections, etc.<br />
* Development (with content area editors) of a Commons ''Style Guide''<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://www.lulu.com/us/en/about/member-agreement Lulu Member Agreement]<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Commons Governance minutes for September 21, 2012 2pm est.<br />
Attendees: Karl, Carol, Chris, Rahul, Reid<br />
Operational behavior of the Commons: content types/ area structures/ workshop materials<br />
how do we manage identifiers<br />
thoughts to the mission or vision<br />
Second half of the mission is almost there<br />
Attributes for how the commons will operate<br />
understanding that content is targeted towards broader audience<br />
permanent record it is not- but persistent record<br />
?tagging scheme<br />
browse-ability tags of access<br />
attribute additions- comment ability<br />
Carol- is this a descriptive tool or part of a vision statement<br />
Chris-Best Visions are short and sweet<br />
attributes are distilled down into brief and compelling<br />
Starting the wording for the vision statement<br />
capturing community knowledge through -the trusted leader in earth science information<br />
something short and direct for vision<br />
Vision: Karl- redefining the boundaries of publishing- doesn't match goal of ESIP separating the tech side from the out come of the Commons<br />
Carol: what is different about it- capturing knowledge that wouldn't otherwise be published grey literature-This is not business as usual- works in progress- <br />
ESIP Commons published the full breadth of knowledge generated by the ESIP community shared within the federation to advance earth science informatics<br />
K: Preserves and organizes: search, browse, ongoing discussion- capture of quality representing ongoing value of materials or knowledge/ Captures and organizes the breadth of knowledge<br />
Carol: shared? may not be the best word- sharing its knowledge<br />
community or breadth<br />
moving to google docs document:<br />
Rahul- is this as much a publishing arm- or … new documentation tool importance from research community- notion of publication<br />
Note for future (Reid-task) add to the list of governance- tagging member vs. non…<br />
we can tag member affiliation without stating member in vision<br />
how to reflect tagging and commenting ?social? not social<br />
Carol - we don't need the support of the informatics community<br />
In the mission we talk about the open, curated, sharing with thte broader community- Do that not just for the sake of the community, but to share with others<br />
Karl: Broad community of users…Meeting capture piece- discussion? is it in there?<br />
Rahul- it is enabled - we don't have control over whether people use it<br />
Carol: dynamic resource- changing content dynamic place, not just contributions but keeps the conversation going<br />
Rahul- systematically rather than organize- systematically applies and simplifies<br />
publishes the breadth of knowledge/ breath of content- diversity of content/ "diverse content contributed by" not supporting, but sharing<br />
content or knowledge- knowledge is not as broad- keeps the material broad<br />
Karl: copy and pasting into wiki: closing google document-<br />
current draft: The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
Next Meeting will be Friday October 5, 2012 at the same time 2pm EST.<br />
<br />
<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41156Commons Steering Committee Workspace2012-10-05T18:51:30Z<p>Kbene: /* Licensing Options and Assignment of License to ESIP */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
==Draft Vision Statement==<br />
<br />
=== Current draft language ===<br />
<br />
The ESIP Commons will be the central destination for the Earth Science community to access and interact with the knowledge of the ESIP Federation<br />
<br />
=== previous ===<br />
The ESIP Commons will be a valued participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
<br><br />
<br />
===Alternative draft language===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science?<br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
* Need to give ESIP Commons permission to republish while author's retain copyright<br />
* Creative Commons as a "preferred" or "only" option for materials posted through the Commons? Public domain?<br />
* Author certification of copyright<br />
* Enable a botton for all content to flag potential copyright violations/issues?<br />
* DMCA process?<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
* Dispute resolution<br />
* Management of overall Commons "structure" - categories, sections, etc.<br />
* Development (with content area editors) of a Commons ''Style Guide''<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://www.lulu.com/us/en/about/member-agreement Lulu Member Agreement]<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Commons Governance minutes for September 21, 2012 2pm est.<br />
Attendees: Karl, Carol, Chris, Rahul, Reid<br />
Operational behavior of the Commons: content types/ area structures/ workshop materials<br />
how do we manage identifiers<br />
thoughts to the mission or vision<br />
Second half of the mission is almost there<br />
Attributes for how the commons will operate<br />
understanding that content is targeted towards broader audience<br />
permanent record it is not- but persistent record<br />
?tagging scheme<br />
browse-ability tags of access<br />
attribute additions- comment ability<br />
Carol- is this a descriptive tool or part of a vision statement<br />
Chris-Best Visions are short and sweet<br />
attributes are distilled down into brief and compelling<br />
Starting the wording for the vision statement<br />
capturing community knowledge through -the trusted leader in earth science information<br />
something short and direct for vision<br />
Vision: Karl- redefining the boundaries of publishing- doesn't match goal of ESIP separating the tech side from the out come of the Commons<br />
Carol: what is different about it- capturing knowledge that wouldn't otherwise be published grey literature-This is not business as usual- works in progress- <br />
ESIP Commons published the full breadth of knowledge generated by the ESIP community shared within the federation to advance earth science informatics<br />
K: Preserves and organizes: search, browse, ongoing discussion- capture of quality representing ongoing value of materials or knowledge/ Captures and organizes the breadth of knowledge<br />
Carol: shared? may not be the best word- sharing its knowledge<br />
community or breadth<br />
moving to google docs document:<br />
Rahul- is this as much a publishing arm- or … new documentation tool importance from research community- notion of publication<br />
Note for future (Reid-task) add to the list of governance- tagging member vs. non…<br />
we can tag member affiliation without stating member in vision<br />
how to reflect tagging and commenting ?social? not social<br />
Carol - we don't need the support of the informatics community<br />
In the mission we talk about the open, curated, sharing with thte broader community- Do that not just for the sake of the community, but to share with others<br />
Karl: Broad community of users…Meeting capture piece- discussion? is it in there?<br />
Rahul- it is enabled - we don't have control over whether people use it<br />
Carol: dynamic resource- changing content dynamic place, not just contributions but keeps the conversation going<br />
Rahul- systematically rather than organize- systematically applies and simplifies<br />
publishes the breadth of knowledge/ breath of content- diversity of content/ "diverse content contributed by" not supporting, but sharing<br />
content or knowledge- knowledge is not as broad- keeps the material broad<br />
Karl: copy and pasting into wiki: closing google document-<br />
current draft: The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
Next Meeting will be Friday October 5, 2012 at the same time 2pm EST.<br />
<br />
<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41155Commons Steering Committee Workspace2012-10-05T18:34:23Z<p>Kbene: /* Current draft language */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
==Draft Vision Statement==<br />
<br />
=== Current draft language ===<br />
<br />
The ESIP Commons will be the central destination for the Earth Science community to access and interact with the knowledge of the ESIP Federation<br />
<br />
=== previous ===<br />
The ESIP Commons will be a valued participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
<br><br />
<br />
===Alternative draft language===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science?<br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
* Need to give ESIP Commons permission to republish while author's retain copyright<br />
* Creative Commons as a "preferred" or "only" option for materials posted through the Commons?<br />
* Author certification of copyright<br />
* Enable a botton for all content to flag potential copyright violations/issues?<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
* Dispute resolution<br />
* Management of overall Commons "structure" - categories, sections, etc.<br />
* Development (with content area editors) of a Commons ''Style Guide''<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://www.lulu.com/us/en/about/member-agreement Lulu Member Agreement]<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Commons Governance minutes for September 21, 2012 2pm est.<br />
Attendees: Karl, Carol, Chris, Rahul, Reid<br />
Operational behavior of the Commons: content types/ area structures/ workshop materials<br />
how do we manage identifiers<br />
thoughts to the mission or vision<br />
Second half of the mission is almost there<br />
Attributes for how the commons will operate<br />
understanding that content is targeted towards broader audience<br />
permanent record it is not- but persistent record<br />
?tagging scheme<br />
browse-ability tags of access<br />
attribute additions- comment ability<br />
Carol- is this a descriptive tool or part of a vision statement<br />
Chris-Best Visions are short and sweet<br />
attributes are distilled down into brief and compelling<br />
Starting the wording for the vision statement<br />
capturing community knowledge through -the trusted leader in earth science information<br />
something short and direct for vision<br />
Vision: Karl- redefining the boundaries of publishing- doesn't match goal of ESIP separating the tech side from the out come of the Commons<br />
Carol: what is different about it- capturing knowledge that wouldn't otherwise be published grey literature-This is not business as usual- works in progress- <br />
ESIP Commons published the full breadth of knowledge generated by the ESIP community shared within the federation to advance earth science informatics<br />
K: Preserves and organizes: search, browse, ongoing discussion- capture of quality representing ongoing value of materials or knowledge/ Captures and organizes the breadth of knowledge<br />
Carol: shared? may not be the best word- sharing its knowledge<br />
community or breadth<br />
moving to google docs document:<br />
Rahul- is this as much a publishing arm- or … new documentation tool importance from research community- notion of publication<br />
Note for future (Reid-task) add to the list of governance- tagging member vs. non…<br />
we can tag member affiliation without stating member in vision<br />
how to reflect tagging and commenting ?social? not social<br />
Carol - we don't need the support of the informatics community<br />
In the mission we talk about the open, curated, sharing with thte broader community- Do that not just for the sake of the community, but to share with others<br />
Karl: Broad community of users…Meeting capture piece- discussion? is it in there?<br />
Rahul- it is enabled - we don't have control over whether people use it<br />
Carol: dynamic resource- changing content dynamic place, not just contributions but keeps the conversation going<br />
Rahul- systematically rather than organize- systematically applies and simplifies<br />
publishes the breadth of knowledge/ breath of content- diversity of content/ "diverse content contributed by" not supporting, but sharing<br />
content or knowledge- knowledge is not as broad- keeps the material broad<br />
Karl: copy and pasting into wiki: closing google document-<br />
current draft: The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
Next Meeting will be Friday October 5, 2012 at the same time 2pm EST.<br />
<br />
<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41154Commons Steering Committee Workspace2012-10-05T18:29:25Z<p>Kbene: /* Current draft language */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
==Draft Vision Statement==<br />
<br />
=== Current draft language ===<br />
The ESIP Commons will be a valued participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
<br><br />
<br />
===Alternative draft language===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science?<br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
* Need to give ESIP Commons permission to republish while author's retain copyright<br />
* Creative Commons as a "preferred" or "only" option for materials posted through the Commons?<br />
* Author certification of copyright<br />
* Enable a botton for all content to flag potential copyright violations/issues?<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
* Dispute resolution<br />
* Management of overall Commons "structure" - categories, sections, etc.<br />
* Development (with content area editors) of a Commons ''Style Guide''<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://www.lulu.com/us/en/about/member-agreement Lulu Member Agreement]<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Commons Governance minutes for September 21, 2012 2pm est.<br />
Attendees: Karl, Carol, Chris, Rahul, Reid<br />
Operational behavior of the Commons: content types/ area structures/ workshop materials<br />
how do we manage identifiers<br />
thoughts to the mission or vision<br />
Second half of the mission is almost there<br />
Attributes for how the commons will operate<br />
understanding that content is targeted towards broader audience<br />
permanent record it is not- but persistent record<br />
?tagging scheme<br />
browse-ability tags of access<br />
attribute additions- comment ability<br />
Carol- is this a descriptive tool or part of a vision statement<br />
Chris-Best Visions are short and sweet<br />
attributes are distilled down into brief and compelling<br />
Starting the wording for the vision statement<br />
capturing community knowledge through -the trusted leader in earth science information<br />
something short and direct for vision<br />
Vision: Karl- redefining the boundaries of publishing- doesn't match goal of ESIP separating the tech side from the out come of the Commons<br />
Carol: what is different about it- capturing knowledge that wouldn't otherwise be published grey literature-This is not business as usual- works in progress- <br />
ESIP Commons published the full breadth of knowledge generated by the ESIP community shared within the federation to advance earth science informatics<br />
K: Preserves and organizes: search, browse, ongoing discussion- capture of quality representing ongoing value of materials or knowledge/ Captures and organizes the breadth of knowledge<br />
Carol: shared? may not be the best word- sharing its knowledge<br />
community or breadth<br />
moving to google docs document:<br />
Rahul- is this as much a publishing arm- or … new documentation tool importance from research community- notion of publication<br />
Note for future (Reid-task) add to the list of governance- tagging member vs. non…<br />
we can tag member affiliation without stating member in vision<br />
how to reflect tagging and commenting ?social? not social<br />
Carol - we don't need the support of the informatics community<br />
In the mission we talk about the open, curated, sharing with thte broader community- Do that not just for the sake of the community, but to share with others<br />
Karl: Broad community of users…Meeting capture piece- discussion? is it in there?<br />
Rahul- it is enabled - we don't have control over whether people use it<br />
Carol: dynamic resource- changing content dynamic place, not just contributions but keeps the conversation going<br />
Rahul- systematically rather than organize- systematically applies and simplifies<br />
publishes the breadth of knowledge/ breath of content- diversity of content/ "diverse content contributed by" not supporting, but sharing<br />
content or knowledge- knowledge is not as broad- keeps the material broad<br />
Karl: copy and pasting into wiki: closing google document-<br />
current draft: The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
Next Meeting will be Friday October 5, 2012 at the same time 2pm EST.<br />
<br />
<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41153Commons Steering Committee Workspace2012-10-05T18:00:46Z<p>Kbene: /* Licensing Options and Assignment of License to ESIP */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
==Draft Vision Statement==<br />
<br />
=== Current draft language ===<br />
The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
<br><br />
<br />
===Alternative draft language===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science?<br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
* Need to give ESIP Commons permission to republish while author's retain copyright<br />
* Creative Commons as a "preferred" or "only" option for materials posted through the Commons?<br />
* Author certification of copyright<br />
* Enable a botton for all content to flag potential copyright violations/issues?<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
* Dispute resolution<br />
* Management of overall Commons "structure" - categories, sections, etc.<br />
* Development (with content area editors) of a Commons ''Style Guide''<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://www.lulu.com/us/en/about/member-agreement Lulu Member Agreement]<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Commons Governance minutes for September 21, 2012 2pm est.<br />
Attendees: Karl, Carol, Chris, Rahul, Reid<br />
Operational behavior of the Commons: content types/ area structures/ workshop materials<br />
how do we manage identifiers<br />
thoughts to the mission or vision<br />
Second half of the mission is almost there<br />
Attributes for how the commons will operate<br />
understanding that content is targeted towards broader audience<br />
permanent record it is not- but persistent record<br />
?tagging scheme<br />
browse-ability tags of access<br />
attribute additions- comment ability<br />
Carol- is this a descriptive tool or part of a vision statement<br />
Chris-Best Visions are short and sweet<br />
attributes are distilled down into brief and compelling<br />
Starting the wording for the vision statement<br />
capturing community knowledge through -the trusted leader in earth science information<br />
something short and direct for vision<br />
Vision: Karl- redefining the boundaries of publishing- doesn't match goal of ESIP separating the tech side from the out come of the Commons<br />
Carol: what is different about it- capturing knowledge that wouldn't otherwise be published grey literature-This is not business as usual- works in progress- <br />
ESIP Commons published the full breadth of knowledge generated by the ESIP community shared within the federation to advance earth science informatics<br />
K: Preserves and organizes: search, browse, ongoing discussion- capture of quality representing ongoing value of materials or knowledge/ Captures and organizes the breadth of knowledge<br />
Carol: shared? may not be the best word- sharing its knowledge<br />
community or breadth<br />
moving to google docs document:<br />
Rahul- is this as much a publishing arm- or … new documentation tool importance from research community- notion of publication<br />
Note for future (Reid-task) add to the list of governance- tagging member vs. non…<br />
we can tag member affiliation without stating member in vision<br />
how to reflect tagging and commenting ?social? not social<br />
Carol - we don't need the support of the informatics community<br />
In the mission we talk about the open, curated, sharing with thte broader community- Do that not just for the sake of the community, but to share with others<br />
Karl: Broad community of users…Meeting capture piece- discussion? is it in there?<br />
Rahul- it is enabled - we don't have control over whether people use it<br />
Carol: dynamic resource- changing content dynamic place, not just contributions but keeps the conversation going<br />
Rahul- systematically rather than organize- systematically applies and simplifies<br />
publishes the breadth of knowledge/ breath of content- diversity of content/ "diverse content contributed by" not supporting, but sharing<br />
content or knowledge- knowledge is not as broad- keeps the material broad<br />
Karl: copy and pasting into wiki: closing google document-<br />
current draft: The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
Next Meeting will be Friday October 5, 2012 at the same time 2pm EST.<br />
<br />
<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41152Commons Steering Committee Workspace2012-10-05T17:59:15Z<p>Kbene: /* Role of Steering Committee */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
==Draft Vision Statement==<br />
<br />
=== Current draft language ===<br />
The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
<br><br />
<br />
===Alternative draft language===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science?<br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
* Need to give ESIP Commons permission to republish while author's retain copyright<br />
* Creative Commons as a "preferred" or "only" option for materials posted through the Commons?<br />
* Author certification of copyright<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
* Dispute resolution<br />
* Management of overall Commons "structure" - categories, sections, etc.<br />
* Development (with content area editors) of a Commons ''Style Guide''<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://www.lulu.com/us/en/about/member-agreement Lulu Member Agreement]<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Commons Governance minutes for September 21, 2012 2pm est.<br />
Attendees: Karl, Carol, Chris, Rahul, Reid<br />
Operational behavior of the Commons: content types/ area structures/ workshop materials<br />
how do we manage identifiers<br />
thoughts to the mission or vision<br />
Second half of the mission is almost there<br />
Attributes for how the commons will operate<br />
understanding that content is targeted towards broader audience<br />
permanent record it is not- but persistent record<br />
?tagging scheme<br />
browse-ability tags of access<br />
attribute additions- comment ability<br />
Carol- is this a descriptive tool or part of a vision statement<br />
Chris-Best Visions are short and sweet<br />
attributes are distilled down into brief and compelling<br />
Starting the wording for the vision statement<br />
capturing community knowledge through -the trusted leader in earth science information<br />
something short and direct for vision<br />
Vision: Karl- redefining the boundaries of publishing- doesn't match goal of ESIP separating the tech side from the out come of the Commons<br />
Carol: what is different about it- capturing knowledge that wouldn't otherwise be published grey literature-This is not business as usual- works in progress- <br />
ESIP Commons published the full breadth of knowledge generated by the ESIP community shared within the federation to advance earth science informatics<br />
K: Preserves and organizes: search, browse, ongoing discussion- capture of quality representing ongoing value of materials or knowledge/ Captures and organizes the breadth of knowledge<br />
Carol: shared? may not be the best word- sharing its knowledge<br />
community or breadth<br />
moving to google docs document:<br />
Rahul- is this as much a publishing arm- or … new documentation tool importance from research community- notion of publication<br />
Note for future (Reid-task) add to the list of governance- tagging member vs. non…<br />
we can tag member affiliation without stating member in vision<br />
how to reflect tagging and commenting ?social? not social<br />
Carol - we don't need the support of the informatics community<br />
In the mission we talk about the open, curated, sharing with thte broader community- Do that not just for the sake of the community, but to share with others<br />
Karl: Broad community of users…Meeting capture piece- discussion? is it in there?<br />
Rahul- it is enabled - we don't have control over whether people use it<br />
Carol: dynamic resource- changing content dynamic place, not just contributions but keeps the conversation going<br />
Rahul- systematically rather than organize- systematically applies and simplifies<br />
publishes the breadth of knowledge/ breath of content- diversity of content/ "diverse content contributed by" not supporting, but sharing<br />
content or knowledge- knowledge is not as broad- keeps the material broad<br />
Karl: copy and pasting into wiki: closing google document-<br />
current draft: The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
Next Meeting will be Friday October 5, 2012 at the same time 2pm EST.<br />
<br />
<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41151Commons Steering Committee Workspace2012-10-05T17:57:22Z<p>Kbene: /* Licensing Options and Assignment of License to ESIP */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
==Draft Vision Statement==<br />
<br />
=== Current draft language ===<br />
The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
<br><br />
<br />
===Alternative draft language===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science?<br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
* Need to give ESIP Commons permission to republish while author's retain copyright<br />
* Creative Commons as a "preferred" or "only" option for materials posted through the Commons?<br />
* Author certification of copyright<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://www.lulu.com/us/en/about/member-agreement Lulu Member Agreement]<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Commons Governance minutes for September 21, 2012 2pm est.<br />
Attendees: Karl, Carol, Chris, Rahul, Reid<br />
Operational behavior of the Commons: content types/ area structures/ workshop materials<br />
how do we manage identifiers<br />
thoughts to the mission or vision<br />
Second half of the mission is almost there<br />
Attributes for how the commons will operate<br />
understanding that content is targeted towards broader audience<br />
permanent record it is not- but persistent record<br />
?tagging scheme<br />
browse-ability tags of access<br />
attribute additions- comment ability<br />
Carol- is this a descriptive tool or part of a vision statement<br />
Chris-Best Visions are short and sweet<br />
attributes are distilled down into brief and compelling<br />
Starting the wording for the vision statement<br />
capturing community knowledge through -the trusted leader in earth science information<br />
something short and direct for vision<br />
Vision: Karl- redefining the boundaries of publishing- doesn't match goal of ESIP separating the tech side from the out come of the Commons<br />
Carol: what is different about it- capturing knowledge that wouldn't otherwise be published grey literature-This is not business as usual- works in progress- <br />
ESIP Commons published the full breadth of knowledge generated by the ESIP community shared within the federation to advance earth science informatics<br />
K: Preserves and organizes: search, browse, ongoing discussion- capture of quality representing ongoing value of materials or knowledge/ Captures and organizes the breadth of knowledge<br />
Carol: shared? may not be the best word- sharing its knowledge<br />
community or breadth<br />
moving to google docs document:<br />
Rahul- is this as much a publishing arm- or … new documentation tool importance from research community- notion of publication<br />
Note for future (Reid-task) add to the list of governance- tagging member vs. non…<br />
we can tag member affiliation without stating member in vision<br />
how to reflect tagging and commenting ?social? not social<br />
Carol - we don't need the support of the informatics community<br />
In the mission we talk about the open, curated, sharing with thte broader community- Do that not just for the sake of the community, but to share with others<br />
Karl: Broad community of users…Meeting capture piece- discussion? is it in there?<br />
Rahul- it is enabled - we don't have control over whether people use it<br />
Carol: dynamic resource- changing content dynamic place, not just contributions but keeps the conversation going<br />
Rahul- systematically rather than organize- systematically applies and simplifies<br />
publishes the breadth of knowledge/ breath of content- diversity of content/ "diverse content contributed by" not supporting, but sharing<br />
content or knowledge- knowledge is not as broad- keeps the material broad<br />
Karl: copy and pasting into wiki: closing google document-<br />
current draft: The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
Next Meeting will be Friday October 5, 2012 at the same time 2pm EST.<br />
<br />
<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41041Commons Steering Committee Workspace2012-09-21T19:07:17Z<p>Kbene: /* Vision */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
==Draft Vision Statement==<br />
<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science?<br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
=== current draft ===<br />
The ESIP Commons is a participatory platform that systematically captures, publishes and shares diverse content contributed by the ESIP Federation.<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41040Commons Steering Committee Workspace2012-09-21T18:44:36Z<p>Kbene: /* Draft Vision Statement */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
== Vision == <br />
<br />
[https://docs.google.com/document/d/1H7H7TkzQbVeyDsbbLp7lXqelZ1a7Xh7tuJcwl6pQSGM/edit Working Draft Google Doc]<br />
<br />
=== Draft Vision Statement ===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science? <br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
The ESIP Commons captures and organizes the shared knowledge of the ESIP Federation in support of the Earth science informatics community.<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
[http://www.youtube.com/t/community_guidelines YouTube Community Guidelines]<br />
<br />
<br />
<br />
[[Media:ESIPiCommons_Requirements.pdf| Original Requirements for ESIP Commons]]<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41036Commons Steering Committee Workspace2012-09-21T18:30:05Z<p>Kbene: /* Differentiation between Web Site, Wiki, and Commons */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
== Vision == <br />
<br />
=== Draft Vision Statement ===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science? <br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
[http://www.youtube.com/t/community_guidelines YouTube Community Guidelines]<br />
<br />
<br />
<br />
[[Media:ESIPiCommons_Requirements.pdf| Original Requirements for ESIP Commons]]<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
<br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41035Commons Steering Committee Workspace2012-09-21T18:29:48Z<p>Kbene: /* Vision */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
== Vision == <br />
<br />
=== Draft Vision Statement ===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science? <br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
[http://www.youtube.com/t/community_guidelines YouTube Community Guidelines]<br />
<br />
<br />
<br />
[[Media:ESIPiCommons_Requirements.pdf| Original Requirements for ESIP Commons]]<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41034Commons Steering Committee Workspace2012-09-21T18:27:15Z<p>Kbene: /* Vision */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
== Vision == <br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
*forum for ongoing comments & discussion around content<br />
<br />
=== Draft Vision Statement ===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science? <br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community knowledge to advance Earth science informatics.<br />
<br />
<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
[http://www.youtube.com/t/community_guidelines YouTube Community Guidelines]<br />
<br />
<br />
<br />
[[Media:ESIPiCommons_Requirements.pdf| Original Requirements for ESIP Commons]]<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=41032Commons Steering Committee Workspace2012-09-21T18:22:50Z<p>Kbene: /* Mission */</p>
<hr />
<div>== Mission==<br />
<br />
=== First Draft ===<br />
The ESIP Commons is a curated, open, knowledge capture repository for documenting contributions to or arising out of the ESIP Federation. The ESIP Commons creates citable content to recognize individual and organizational contributions to the community. The ESIP Commons provides the larger Earth science informatics community with browsable, discoverable and reusasble resources to move forward faster and more effectively than they could have along.<br />
<br />
=== Current Draft ===<br />
The ESIP Commons is a curated, open access knowledge repository for publishing contributions to or arising out of the ESIP Federation. The ESIP Commons is a publication platform:<br />
:* for citable content to recognize individual and organizational contributions to the community and<br />
:* for accelerating the discovery and use of knowledge by the global Earth science informatics community.<br />
<br />
== Vision == <br />
=== Attributes ===<br />
*capturing quality information<br />
*lightweight publication review (aka sniff test)<br />
*reputation growth (individual & organizational)<br />
*persistent content (curation through time provides documentation and evidence of growth and change)<br />
*documents work of ESIP, including meetings<br />
*citable (DOIs are easy to link to- sustainable mostly)<br />
*discoverability (e.g. thru tagging)<br />
*browsability<br />
<br />
=== Draft Vision Statement ===<br />
The ESIP Commons realizes the full wealth of expertise and knowledge housed within the ESIP Community in order to move the entire Earth science data and informatics forward toward better science? <br />
<br />
The ESIP Commons redefines the boundaries of publishing to capture community <br />
<br />
<br />
<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
<br />
<br />
[http://www.youtube.com/t/community_guidelines YouTube Community Guidelines]<br />
<br />
<br />
<br />
[[Media:ESIPiCommons_Requirements.pdf| Original Requirements for ESIP Commons]]<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
*Website - 'Brochure'/Marketing/Organizational Site, Assumes no prior knowledge, Primarily External Facing, Portal (?)/ linking element, to other web presences, Heavily Moderated/Managed content, more static<br />
*Wiki - ESIP Community Workspace, Prior Knowledge Useful as Wiki Difficult to Navigate, Business of the ESIP Federation, Primarily Internal Facing, self moderation, constantly changing<br />
*Commons - Curated Content, Knowledge Capture, Internal & External Facing, Content Available in Perpetuity, Light-touch management and moderation<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
== Miscellaneous Discussion Items ==<br />
<br />
*Levels of curation<br />
*Who Contributed? (community, individual)<br />
*Comment-Ability (is it set always?) and community accountability through flags as opposed to moderators- (is that too wiki-like?)<br />
<br />
== Resources ==<br />
<br />
[http://en.wikipedia.org/wiki/Gray_literature Gray Literature]<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
[http://en.wikipedia.org/wiki/Wikipedia:Community_portal Wikipedia Community Portal]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia Policies & Guidelines]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_administration.2C_oversight.2C_and_management Wikipedia Editorial Administration & Oversight]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Handling_disputes_and_abuse Wikipedia Handling Disputes]<br />
:[http://en.wikipedia.org/wiki/Wikipedia:About#Editorial_quality_review Wikipedia Editorial Quality Review]<br />
<br />
[http://commons.wikimedia.org/wiki/Commons:Community_portal Wikimedia Commons Community Portal]<br />
:[http://commons.wikimedia.org/wiki/Commons:Project_scope Wikimedia Commons Project Scope]<br />
<br />
[http://www.flickr.com/help/guidelines/ Flickr Community Guidelines]<br />
<br />
[http://www.eoearth.org/articles/view/158844/?topic=63435 Encyclopedia of Earth Guidelines]<br />
<br />
== Anticipated Budget ==<br />
<br />
== Minutes ==<br />
Minutes from Commons Governance Telecon for Friday August 24; 2-3:15 pm EST<br />
Attendees:<br />
Erin, Karl, Rahul, Carol, Reid<br />
Continued conversation about the straw man draft of the vision statement<br />
viewing resources for developing policies and level and design of management <br />
Carol:<br />
evolution of commons reflected from the initial to current to future<br />
Erin and Carol youTube channel idea-name-commons may not reflect the mission entirely<br />
Karl- ways to aggregate using content types<br />
<br />
Commons: is a gathering spot- not to call it something different, but for purpose of understanding vision<br />
<br />
Rahul- likes the iCommons original<br />
<br />
channel: filtered content<br />
subscribe to channels<br />
<br />
Curation: long term access evaluation and classification<br />
weaker association but needs to be highlighted<br />
<br />
Mission diving in:<br />
curated and open<br />
contributions to and arising out of - individual contribute to group product: products of federation activities<br />
who contributes: members/ is there a prerequisite?<br />
Scope- community guidelines for contribution<br />
Term for contributors; community more encompassing concept<br />
Member affiliated and non-member affiliated contributions<br />
broadly available for community<br />
Carol- how do you manage those contributions<br />
Flagging system- capture that on-going feedback<br />
Post publication peer review process: how that relates to a flagging system<br />
Binary thing<br />
Caution with community- rivalry<br />
Policies deal with this<br />
Mission stays broad to allow for growth (Erin)<br />
More moderation the more open…<br />
YouTube a good example of moderation experiences- complaints about the comments; active moderation- moderated out<br />
Karl- anchor terms guidelines to help us define.<br />
Rahul- Open as open publish or open to members- Notion of publications needs to be in there.<br />
Grey lit?<br />
- is it negative<br />
Not-formally published but Karl- redefining publication<br />
Open-Access (say explicitly) <br />
Publication- Is it publishing- publication platform - Evolving? Like Publication Platform<br />
Content- back to ESIP mission <br />
<br />
Erin: Community Guidance and Guidelines- the place where this gets specific<br />
Karl- items that would go in to the commons that aren't Earth science<br />
Curation is- filtration<br />
Context up front- Carol- Mission will not be stand alone- other web presence<br />
Hooks from the mission into the vision- logical flow<br />
Linking the functional sectors of observation, research, <br />
Karl: accelerates the discovery and use of that knowledge by the broader Earth Science informatics community<br />
Carol- run-on tends to lose people<br />
Karl- Emphasis on recognition<br />
Carol- colon and bullet the two thoughts<br />
<br />
from Rahul Ramachanadran to Everyone:<br />
The Earth Science Informatics will help to develop and shape the new field of Earth Science Informatics. It is intended to provide a dissemination platform for research using systems-based approaches to solve multi-scale Earth science problems by encouraging the development …..<br />
dissemination or publication platform<br />
Carol- publication is more concrete more action<br />
acceleration<br />
Community contributions bracketed- should brackets be removed community redundant<br />
develop and shape- for vision<br />
publishing transformation in vision<br />
Moving onto vision<br />
peer - reviewed in an open-access platform<br />
realizing the wealth of expertise - shape and develop<br />
Vision is …something out there- what you are going to work toward<br />
The ESIP Commons redefines the boundaries of publishing to document the dynamic…<br />
content is living-Erin<br />
Karl- dichotomy of evolving knowledge and establishment of a public platform that defines pieces of knowledge that remain static….<br />
conversation around the content is dynamic- another facet<br />
anyone can archive papers this is broader through linkage<br />
evolving perspective about that<br />
institutional memory/ community memory<br />
capture - other words for memory<br />
Talk about vision next week <br />
Meeting scheduled for 2:30pm EST In the meantime look at Wiki and edit/ add ideas as thoughts occur<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 13:49, 24 August 2012 (MDT)<br />
<br />
<br />
<br />
'''<br />
Minutes from meeting August 17, 2012'''<br />
Governance issues and the management of the commons:<br />
Visions: link to original concept by Rahul- subset of the directions that the original concept is current- going towards a subset of what we discussed at the summer meeting<br />
Role of the wiki-complementary commons and initial web site<br />
venn-diagram of the intersection<br />
curation model - key idea of curation<br />
licensing- everyone on the same page what licenses are most needed<br />
rights that are most need with respect to access<br />
<br />
What is the role of the steering committee or other management- "managing editor"- handling disputes/ questions?<br />
Look at PlosOne license adoption as exemplar<br />
Wikipedia document proxesses and wikipedia commons<br />
Fickr- guidelines and policies<br />
resources: financial needs for support or maintenance: time to think about funding<br />
point of departure: thinking about the vision and the curation model<br />
differentiation- also can gain from looking at the other sites<br />
functionality- web assests that are part of an overall presence<br />
area of overlap- workflows, contents, how can we cross reference or link between them<br />
commonality/ look and feel: coherent brand<br />
capturing differences and similarities<br />
web site proper has been online brochure: external facing- no prior knowledge<br />
wiki- active collaboration- about or within activity areas work with each other- even though remote<br />
approachability is challenge: where to find the granularity of information<br />
Chris: Tangent Points- link not a lot of overlap -different types of links into the commons- drill down<br />
Conceptual differences- contents will be where?<br />
Who the audience of the Commons is:<br />
hybrid: external component<br />
also way for self documentation<br />
external component may be more dominant in determining sort of polish<br />
audience may not have as much familiarity with the inter workings <br />
professionalism in the products<br />
strengthens reputations beyond the community<br />
<br />
Creating:<br />
style guide: what should be included<br />
work flow- lower the barriers without going too low that quality<br />
ESIP community generated content- community contributions- do we review those?<br />
self curation with products<br />
criteria for poster; (Flickr community guidelines)<br />
working definitions for these three entities: create a table catalogue with content types- style guides standards<br />
Creating a document with all these principles- available in perpetuity<br />
<br />
Defining:<br />
wiki- ephemera<br />
commons current snapshot<br />
looking at the encyclopedia of Earth http://www.eoearth.org/<br />
capturing quality information with user feedback: opportunity within the commons<br />
lightweight publication workflow<br />
helps define use for application purposes- pushes discussion among the community<br />
<br />
Planning<br />
Erin and Carol: Strawman vision for editing<br />
Capturing Commons to inform:<br />
reputation: individual and organizational<br />
demonstration of productivity- concrete ability to show other program managers<br />
discoverability and browse ability (judicious use of tagging and other schemes- aggregate lists of contents)<br />
models- resources- refer to those in next conversation<br />
- reconvene and discuss the draft via Erin and Carol<br />
<br />
Call next Friday 2pm EST webex<br />
--[[User:Reidboehm|Reidboehm]] ([[User talk:Reidboehm|talk]]) 14:17, 20 August 2012 (MDT)</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=40516Commons Steering Committee Workspace2012-08-17T00:51:34Z<p>Kbene: /* Resources */</p>
<hr />
<div>== Vision ==<br />
<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
<br />
== Resources ==<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
== Anticipated Budget ==</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=40515Commons Steering Committee Workspace2012-08-17T00:50:59Z<p>Kbene: /* Resources */</p>
<hr />
<div>== Vision ==<br />
<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
<br />
== Resources ==<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
[http://www.plosone.org/static/submissionInstructions.action PLOS One Submission Instructtions]<br />
<br />
== Anticipated Budget ==</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=40514Commons Steering Committee Workspace2012-08-17T00:43:58Z<p>Kbene: /* Resources */</p>
<hr />
<div>== Vision ==<br />
<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
<br />
== Resources ==<br />
<br />
[http://www.plosone.org/static/license.action PLOS One License]<br />
<br />
== Anticipated Budget ==</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=40513Commons Steering Committee Workspace2012-08-16T20:37:48Z<p>Kbene: </p>
<hr />
<div>== Vision ==<br />
<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
<br />
<br />
== Curation Model ==<br />
<br />
* Content Types linked to curators<br />
* Tags for faceted aggregation of content<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
<br />
== Resources ==<br />
<br />
<br />
<br />
== Anticipated Budget ==</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=40512Commons Steering Committee Workspace2012-08-16T20:36:06Z<p>Kbene: </p>
<hr />
<div>== Vision ==<br />
<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
<br />
<br />
== Curation Model ==<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
<br />
== Resources ==<br />
<br />
<br />
<br />
== Anticipated Budget ==</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Commons_Steering_Committee_Workspace&diff=40511Commons Steering Committee Workspace2012-08-16T20:34:49Z<p>Kbene: Created page with "== Vision == == Differentiation between Web Site, Wiki, and Commons == == Curation Model == == Licensing Options and Assignment of License to ESIP == == Role of St..."</p>
<hr />
<div>== Vision ==<br />
<br />
<br />
<br />
== Differentiation between Web Site, Wiki, and Commons ==<br />
<br />
<br />
<br />
== Curation Model ==<br />
<br />
<br />
<br />
== Licensing Options and Assignment of License to ESIP ==<br />
<br />
<br />
<br />
== Role of Steering Committee ==<br />
<br />
* Managing Editor(s)<br />
<br />
<br />
<br />
== Anticipated Budget ==</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Main_Page&diff=40510Main Page2012-08-16T20:30:01Z<p>Kbene: /* Administration */</p>
<hr />
<div><big>'''Welcome to the ESIP Federation Wiki'''</big> <br />
<br />
The [http://esipfed.org Federation of Earth Science Information Partners (ESIP)] is a broad-based, distributed community of data and information technology practitioners who come together to collaborate on coordinated interoperability efforts across Earth science communities. <br />
<br />
__TOC__ <br />
==Meetings==<br />
The Earth Science Information Partner (ESIP) Federation meets twice annually, January and July. The meetings each take on a different focus. The winter meeting, held the first week of January each year in Washington, DC has a focus on higher level policy issues. The summer meeting, typically held in July (the week varies) moves around the country to different locations. The summer meeting is technical in nature. The meetings supplement interactions throughout the year by offering concentrated blocks of time to work collaboratively on issues of interest to the community. Each meeting has a theme, ranging from evaluating the impacts of data to defining data and information quality. Feel free to join us at an upcoming ESIP Federation meeting. Links to such meetings are found below.<br />
<br />
: [[Summer_2012_Meeting|July 17-20, 2012 ESIP Summer Meeting, Madison, WI]] ([[Summer_2012_Program|Meeting Agenda]])<br />
:[[Past Meetings]]<br />
:[[Visioneers]]<br />
<br />
== Collaboration Areas == <br />
Participation in the ESIP Federation allows members to expose, gather and enhance their own in-house capabilities in support of an organization’s own mandates. Ultimately, these collaborations enhance the success of data interoperability efforts. The ESIP Federation has a 13-year track record of working on Earth science interoperability solutions that connect distributed and heterogeneous communities through the application of broad community technical expertise.<br />
<br />
'''Quick links''': [http://esipfed.org/collaboration-areas List of all Collab List-Servs] | [http://esipfed.org/telecons Telecon Calendar] | [http://esipfed.webex.com WebEx]<br />
<br />
===Data and Informatics Collaborations===<br />
:[[Cloud Computing|Cloud Computing]]<br />
:[[Decisions]]<br />
:[[Discovery_Cluster|Discovery]] (formerly [[Federated Search]])<br />
:[[:Category:Documentation_Cluster|Documentation]]<br />
:[[Drupal Working Group]]<br />
:[[Earth Science Collaboratory]]<br />
:[[Geospatial]]<br />
:[[Information Quality]]<br />
:[[Interoperability and Technology|Information Technology and Interoperability]]<br />
:[[Preservation and Stewardship]]<br />
:[[Products and Services]]<br />
:[[Semantic Web]]<br />
:[[SPG_Agenda_July_12_2011| SPG Summer 2011 workshop]]<br />
:[[Sensor Web]] ''(Inactive)''<br />
:[[Visualization]]<br />
:[[Web Services]] ''(Inactive)''<br />
<br />
===Societal Benefit Area Collaborations===<br />
:[[Image:Silver Falls OR.JPG|left|Silver Falls, OR]]<br />
:[[Air Quality Work Group | Air Quality]]<br />
:[[Carbon]] ''(inactive)''<br />
:[[Coastal Management]] ''(inactive)''<br />
:[[Disaster Management]] ''(inactive)''<br />
:[[Ecological Forecasting]] ''(inactive)''<br />
:[[Energy and Climate]]<br />
:[[Public Health]] ''(inactive)''<br />
:[[Water Management]] ''(inactive)''<br />
<br />
===Education and Outreach Collaborations===<br />
<br />
:[[Commercial Development]] ''(inactive)''<br />
:[[Education]]<br />
:: [[Climate Education Working Group]]<br />
:: [[Internal ESIP Education Working Group]]<br />
:[[ESIP Expertise]]<br />
:[[Ongoing Topical Webinar Series]] ''(inactive)''<br />
:[[Data Management Workshop|Workshop on Data Management]] ''(inactive)''<br />
:[[Data Management Short Course|Data Management Training]]<br />
:[[Student Cluster]]<br />
<br />
==Administration==<br />
:Committees<br />
::[[Constitution and Bylaws]]<br />
::[[Executive Committee]]<br />
::[[Finance]]<br />
::[[Partnership]]<br />
:Awards<br />
::[http://esipfed.org/charles-falkenberg-award Charles Falkenberg Award]]<br />
::[http://esipfed.org/martha-maiden-award Martha Maiden Award]]<br />
::[http://esipfed.org/presidents-award President's Award]<br />
::[http://esipfed.org/esip-year-partner-award ESIP of the Year]<br />
:Documents<br />
::[[Copyright Policy]]<br />
::[[Federation Documents|Defining Documents]]<br />
::[[Commons Steering Committee Workspace]]<br />
<br />
==Member Resources==<br />
:[http://esipfed.org/esip-faqs FAQ]<br />
:Collaboration Tools<br />
::[[Cluster tools]]<br />
::[[FUNding Friday Projects]]<br />
::[[Demonstrations|Demonstrations]]<br />
::[[Discovery]] ''(Inactive)''<br />
::[[Earth Information Exchange]] ''(Inactive)''<br />
::[[Testbed]]<br />
:Opportunities<br />
::[http://esipfed.org/Funding Funding]<br />
::[http://esipfed.org/jobs Jobs]<br />
:Members<br />
::[http://esipfed.org/content/network Partner List]<br />
:White Papers<br />
::[[Unique Object Identifiers]]<br />
::EarthCube<br />
:::[[media:ESIP101_NSF_Aug2011v3.pdf|ESIP & EarthCube Presentation to NSF]]<br />
:::[[EarthCube Design Approach]]</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Program_Committee&diff=40420Program Committee2012-08-09T17:55:38Z<p>Kbene: /* Agenda */</p>
<hr />
<div>==Executive Committee of the ESIP Federation==<br />
<br />
===Members===<br />
*Karl Benedict, President<br />
*Annette Schloss, Vice President<br />
*Charles Hutchinson, Chair, Ficom<br />
*John Scialdone, Chair, Partnership<br />
*Chris Lenhardt, Chair, C&B<br />
*Sayeed Choudhury, Type I Rep<br />
*Brian Wilson, Type II Rep<br />
*Stefan Falke, Type III Rep<br />
*Curt Tilmes, Chair, Data Stewardship<br />
*Becky Reid, Chair, Education<br />
*Matt Austin, Chair, IT & I<br />
*Ken Keiser, Chair, Products and Services<br />
<br />
===Activities===<br />
====Telecons====<br />
<br />
Next Telecon, August 9, 2012 at 2 EDT<br><br />
<br />
=====Agenda=====<br />
<br />
:1. Approval of [[Draft Excom Minutes| June minutes]]<br />
:2. Excom Business<br />
:* Summer Meeting Wrap Up ([[Media:0712MeetingEvalSummary.pdf|Meeting Evaluation Summary]])<br />
:* Future Summer Meeting Cycles (2013-2016)<br />
:* FY 13 Committee Budget Requests<br />
:* State of the Art Documents<br />
:* Commons Governance Update ([http://commons.esipfed.org/node/448 Session Notes])<br />
:* Awards subgroup Update<br />
:4. Committee Reports <br><br />
:5. Other Business<br />
<br />
=====Supporting Documents=====<br />
[[media:stateOfTheArt.doc | Draft State of the Art Template]]<br />
<br />
====Minutes from recent telecons====<br />
[[Draft Excom Minutes]]<br><br />
[[Approved Excom Minutes]]<br><br />
<br />
===Working Groups and Clusters===<br />
There are currently no active workgroups. To view historic workgroups see: [[ExCom_Inactive_Workgroups|Inactive ExCom workgroups]]<br />
<br />
====Miscellaneous====<br />
[[Raskin Scholarship]]</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Program_Committee&diff=39302Program Committee2012-05-10T18:06:20Z<p>Kbene: /* Members */</p>
<hr />
<div>==Executive Committee of the ESIP Federation==<br />
<br />
===Members===<br />
*Karl Benedict, President<br />
*Annette Schloss, Vice President<br />
*Charles Hutchinson, Chair, Ficom<br />
*John Scialdone, Chair, Partnership<br />
*Chris Lenhardt, Chair, C&B<br />
*Sayeed Choudhury, Type I Rep<br />
*Brian Wilson, Type II Rep<br />
*Stefan Falke, Type III Rep<br />
*Curt Tilmes, Chair, Data Stewardship<br />
*Becky Reid, Chair, Education<br />
*Matt Austin, Chair, IT & I<br />
*Ken Keiser, Chair, Products and Services<br />
<br />
===Activities===<br />
====Telecons====<br />
<br />
Next Telecon, May 10, 2012 at 2 EDT<br><br />
<br />
=====Agenda=====<br />
<br />
1. Approval of [[Draft Excom Minutes| April minutes]]<br><br />
2. Summer Meeting Update <br><br />
3. Energy & Climate Cluster Working Group proposal ([http://wiki.esipfed.org/index.php/Energy_and_Climate Draft White Paper]) <br><br />
4. ESIP Commons Governance Working Group [[ESIP Commons Governance Working Group| proposal]]<br><br />
5. Other Business <br><br />
:*Committee Reports <br><br />
:* <br><br />
<br />
=====Supporting Documents=====<br />
[[media:stateOfTheArt.doc | Draft State of the Art Template]]<br />
<br />
====Minutes from recent telecons====<br />
[[Draft Excom Minutes]]<br><br />
[[Approved Excom Minutes]]<br><br />
<br />
===Working Groups and Clusters===<br />
There are currently no active workgroups. To view historic workgroups see: [[ExCom_Inactive_Workgroups|Inactive ExCom workgroups]]<br />
<br />
====Miscellaneous====<br />
[[Raskin Scholarship]]</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=ESIP_Commons_Governance_Working_Group&diff=39301ESIP Commons Governance Working Group2012-05-10T17:56:01Z<p>Kbene: Created page with "Initial Proposal for moving forward with defining a governance model for content management within the ESIP Commons # Create a working group to define baseline set of Commons do..."</p>
<hr />
<div>Initial Proposal for moving forward with defining a governance model for content management within the ESIP Commons<br />
<br />
# Create a working group to define baseline set of Commons document requirements, upon which document collection teams can build for their particular collection<br />
# Consider a model where there is a high-level "steering committee" for the Commons with much of the "on the ground" document collection management/workflow being handled by teams associated with each collection, for which there are published requirements/guidelines, and procedures.</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Program_Committee&diff=39300Program Committee2012-05-10T17:51:44Z<p>Kbene: /* Agenda */</p>
<hr />
<div>==Executive Committee of the ESIP Federation==<br />
<br />
===Members===<br />
*Karl Benedict, President<br />
*Annette Schloss, Vice President<br />
*Charles Hutchinson, Chair, Ficom<br />
*John Scialdone, Chair, Partnership<br />
*Rob Raskin, Chair, C&B<br />
*Sayeed Choudhury, Type I Rep<br />
*Brian Wilson, Type II Rep<br />
*Stefan Falke, Type III Rep<br />
*Curt Tilmes, Chair, Data Stewardship<br />
*Becky Reid, Chair, Education<br />
*Matt Austin, Chair, IT & I<br />
*Ken Keiser, Chair, Products and Services<br />
<br />
===Activities===<br />
====Telecons====<br />
<br />
Next Telecon, May 10, 2012 at 2 EDT<br><br />
<br />
=====Agenda=====<br />
<br />
1. Approval of [[Draft Excom Minutes| April minutes]]<br><br />
2. Summer Meeting Update <br><br />
3. Energy & Climate Cluster Working Group proposal ([http://wiki.esipfed.org/index.php/Energy_and_Climate Draft White Paper]) <br><br />
4. ESIP Commons Governance Working Group [[ESIP Commons Governance Working Group| proposal]]<br><br />
5. Other Business <br><br />
:*Committee Reports <br><br />
:* <br><br />
<br />
=====Supporting Documents=====<br />
[[media:stateOfTheArt.doc | Draft State of the Art Template]]<br />
<br />
====Minutes from recent telecons====<br />
[[Draft Excom Minutes]]<br><br />
[[Approved Excom Minutes]]<br><br />
<br />
===Working Groups and Clusters===<br />
There are currently no active workgroups. To view historic workgroups see: [[ExCom_Inactive_Workgroups|Inactive ExCom workgroups]]<br />
<br />
====Miscellaneous====<br />
[[Raskin Scholarship]]</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Raskin_Scholarship&diff=38953Raskin Scholarship2012-04-09T14:24:04Z<p>Kbene: /* Next Steps */</p>
<hr />
<div>In the wake of Rob Raskin's untimely death, his family has approached the Foundation for Earth Science/ESIP Federation to explore the possibility of establishing a scholarship in memory of Rob and to preserve his community-minded legacy for generations to come. This page serves as a workplace for the small task team (Rob's colleagues, his family and ESIP leadership) to share ideas and to sharpen the focus of the scholarship idea.<br />
<br />
====Task Team Members====<br />
Family: Lisa Steele<br />
JPL: Ed Armstrong, Chris Mattman, Victor Zlotnicki<br><br />
Collaborators: Peter Fox, Phil Yang<br><br />
ESIP Leadership: Karl Benedict, Annette Schloss<br><br />
Staff: Carol Meyer, Erin Robinson<br><br />
<br />
====Desired Impact====<br />
To provide scholarship support for students of the next generation of Earth science data/technology/informatics leaders...<br />
<br />
===="Scholarship"====<br />
:*Tuition support<br />
:*Student stipend<br />
:*Travel support to ESIP Meeting<br />
:*Research support<br />
:*Internship within ESIP member organizations<br />
:*<br />
:*<br />
<br />
====Thematic Focus====<br />
*Semantics<br />
*Cyberinfrastructure<br />
*GIS - particularly improved accessibility and usability of Earth Science data within GIS environments<br />
*Computers in Geosciences<br />
*Collaboration<br />
*<br />
*<br />
*<br />
<br />
====Next Steps====<br />
*Continue to Iterate on Scope/Focus (All)<br />
*Legal Requirements (Meyer)<br />
*Financial Requirements for Sustainability -- how much funds do we need to keep the fund going? - this will depend upon some of the options selected above.<br />
*</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Raskin_Scholarship&diff=38952Raskin Scholarship2012-04-09T14:23:13Z<p>Kbene: /* Thematic Focus */</p>
<hr />
<div>In the wake of Rob Raskin's untimely death, his family has approached the Foundation for Earth Science/ESIP Federation to explore the possibility of establishing a scholarship in memory of Rob and to preserve his community-minded legacy for generations to come. This page serves as a workplace for the small task team (Rob's colleagues, his family and ESIP leadership) to share ideas and to sharpen the focus of the scholarship idea.<br />
<br />
====Task Team Members====<br />
Family: Lisa Steele<br />
JPL: Ed Armstrong, Chris Mattman, Victor Zlotnicki<br><br />
Collaborators: Peter Fox, Phil Yang<br><br />
ESIP Leadership: Karl Benedict, Annette Schloss<br><br />
Staff: Carol Meyer, Erin Robinson<br><br />
<br />
====Desired Impact====<br />
To provide scholarship support for students of the next generation of Earth science data/technology/informatics leaders...<br />
<br />
===="Scholarship"====<br />
:*Tuition support<br />
:*Student stipend<br />
:*Travel support to ESIP Meeting<br />
:*Research support<br />
:*Internship within ESIP member organizations<br />
:*<br />
:*<br />
<br />
====Thematic Focus====<br />
*Semantics<br />
*Cyberinfrastructure<br />
*GIS - particularly improved accessibility and usability of Earth Science data within GIS environments<br />
*Computers in Geosciences<br />
*Collaboration<br />
*<br />
*<br />
*<br />
<br />
====Next Steps====<br />
*Continue to Iterate on Scope/Focus (All)<br />
*Legal Requirements (Meyer)<br />
*Financial Requirements for Sustainability -- how much funds do we need to keep the fund going?<br />
*</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Raskin_Scholarship&diff=38951Raskin Scholarship2012-04-09T14:22:11Z<p>Kbene: /* "Scholarship" */</p>
<hr />
<div>In the wake of Rob Raskin's untimely death, his family has approached the Foundation for Earth Science/ESIP Federation to explore the possibility of establishing a scholarship in memory of Rob and to preserve his community-minded legacy for generations to come. This page serves as a workplace for the small task team (Rob's colleagues, his family and ESIP leadership) to share ideas and to sharpen the focus of the scholarship idea.<br />
<br />
====Task Team Members====<br />
Family: Lisa Steele<br />
JPL: Ed Armstrong, Chris Mattman, Victor Zlotnicki<br><br />
Collaborators: Peter Fox, Phil Yang<br><br />
ESIP Leadership: Karl Benedict, Annette Schloss<br><br />
Staff: Carol Meyer, Erin Robinson<br><br />
<br />
====Desired Impact====<br />
To provide scholarship support for students of the next generation of Earth science data/technology/informatics leaders...<br />
<br />
===="Scholarship"====<br />
:*Tuition support<br />
:*Student stipend<br />
:*Travel support to ESIP Meeting<br />
:*Research support<br />
:*Internship within ESIP member organizations<br />
:*<br />
:*<br />
<br />
====Thematic Focus====<br />
*Semantics<br />
*Cyberinfrastructure<br />
*GIS<br />
*Computers in Geosciences<br />
*Collaboration<br />
*<br />
*<br />
*<br />
<br />
====Next Steps====<br />
*Continue to Iterate on Scope/Focus (All)<br />
*Legal Requirements (Meyer)<br />
*Financial Requirements for Sustainability -- how much funds do we need to keep the fund going?<br />
*</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=File:Topical_Focus_Document_Template_V2.doc&diff=38399File:Topical Focus Document Template V2.doc2012-02-27T21:33:30Z<p>Kbene: uploaded a new version of &quot;File:Topical Focus Document Template V2.doc&quot;</p>
<hr />
<div>Revised state of the art template</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Summer_2012_Meeting&diff=38394Summer 2012 Meeting2012-02-27T19:41:09Z<p>Kbene: </p>
<hr />
<div>===Location===<br />
University of Wisconsin-Madison<br />
:Most sessions will be held at the UW Pyle Center. Lodging will be offered at a variety of hotels near campus.<br />
<br />
===Dates===<br />
July 17-20, 2012<br />
<br />
===Theme Ideas===<br />
* [[ESIP_and_Innovation|ESIP and Innovation]]<br />
*Earth Science Collaboratory<br />
*Innovation Through Collaboration<br />
*Training and Professional Development<br />
*Innovation Through Collaboration: Leveraging ...<br />
*Innovation and Networking<br />
*Associating, experimenting, collaboration, observing, inspiring<br />
*ESIP Federation: Knowledge Fusion for Innovation<br />
*Exposing Innovation for Individual and Community Benefit<br />
*History and Aspirations in Earth Science Innovation<br />
*A Grand Challenge and corresponding alternative solutions<br />
*<br />
<br />
===Potential Plenary Speakers===<br />
* Joi Ito<br />
* David Bollier (the commons as a source of innovation) [[User:Bcaron|bruce c]]<br />
<br />
===Identified Sessions===<br />
A formal call for sessions will be launched in February 2012. Inquiries have been made about holding sessions on the following:<br />
*DataONE User Working Group (July 15-16)<br />
*NASA Standards Process WG (expected)<br />
*US GIN Workshop (expected)<br />
*Evaluation Workshop (expected)<br />
*Communication Workshop (possible)<br />
*Global Change Information System (possible)<br />
<br />
<br />
===Local Things to Do===<br />
:*A cruise on one of the lakes - private charter or reserved seats on a public cruise <br />
::http://www.bettyloucruises.com/<br />
<br />
:*Madison Mallards Game (home games on the 12th, 13th & 14th):<br />
::http://www.mallardsbaseball.com/<br />
<br />
:*Tours of the Capital <br />
::http://www.wisconsin.gov/state/core/wisconsin_state_capitol_tour.html<br />
<br />
'''Weekend Activities'''<br />
:*Frank Lloyed Wright Taliesin Estate <br />
::http://www.taliesinpreservation.org/<br />
<br />
:*Madison Farmers Market on Saturday mornings:<br />
::http://www.dcfm.org/aboutmkt.asp</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=File:StateOfTheArt.doc&diff=38187File:StateOfTheArt.doc2012-02-09T18:49:13Z<p>Kbene: uploaded a new version of &quot;File:StateOfTheArt.doc&quot;</p>
<hr />
<div>This is the document template that we would like to use for documenting our periodic state of the art in their domain.</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Program_Committee&diff=38186Program Committee2012-02-09T18:10:01Z<p>Kbene: </p>
<hr />
<div>==Executive Committee of the ESIP Federation==<br />
<br />
===Members===<br />
*Karl Benedict, President<br />
*Annette Schloss, Vice President<br />
*Charles Hutchinson, Chair, Ficom<br />
*John Scialdone, Chair, Partnership<br />
*Rob Raskin, Chair, C&B<br />
*Sayeed Chodhury, Type I Rep<br />
*Brian Wilson, Type II Rep<br />
*Stefan Falke, Type III Rep<br />
*Curt Tilmes, Chair, Data Stewardship<br />
*Becky Reid, Chair, Education<br />
*Matt Austin, Chair, IT & I<br />
*Ken Keiser, Chair, Products and Services<br />
<br />
===Activities===<br />
====Telecons====<br />
<br />
Next Telecon, February 9, 2012 at 2 EST<br><br />
<br />
=====Agenda=====<br />
<br />
1. Approval of [[Draft Excom Minutes| January minutes]]<br><br />
2. Summer Meeting Planning<br><br />
:*Theme (http://wiki.esipfed.org/index.php/Summer_2012_Meeting)<br />
:*FUNding Friday<br />
3. Committee, Cluster, Working Group Template<br><br />
4. Committee Updates<br />
:*Products and Services testbed<br />
:*IT&I<br />
5. Other Business<br><br />
<br />
=====Supporting Documents=====<br />
[[media:stateOfTheArt.doc | Draft State of the Art Template]]<br />
<br />
====Minutes from recent telecons====<br />
[[Draft Excom Minutes]]<br><br />
[[Approved Excom Minutes]]<br><br />
<br />
===Working Groups and Clusters===<br />
There are currently no active workgroups. To view historic workgroups see: [[ExCom_Inactive_Workgroups|Inactive ExCom workgroups]]</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=File:StateOfTheArt.doc&diff=38184File:StateOfTheArt.doc2012-02-09T18:05:03Z<p>Kbene: This is the document template that we would like to use for documenting our periodic state of the art in their domain.</p>
<hr />
<div>This is the document template that we would like to use for documenting our periodic state of the art in their domain.</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Summer_2011_Meeting_-_Session_Details&diff=33798Summer 2011 Meeting - Session Details2011-07-12T12:31:31Z<p>Kbene: /* Teacher Workshop */</p>
<hr />
<div>[[Summer_2011_Meeting#Agenda_by_Day|< Back to Summer Meeting Main Page]]<br />
<br />
&nbsp;<br />
<hr><br />
<br />
=Data Science/Life-Cycle=<br />
Information/Data quality-related sessions are marked with an *<br />
<br />
==[[SPG Agenda July 12 2011|Standards and Reference Architectures for NASA Earth Science Data Systems]] *==<br />
We'll be inviting speakers to talk about success stories of implementing/using standards in their data systems. The standards can either be SPG endorsed standards, OGC standards, ISO standards, or de facto standards that might be candidates for the SPG standards process.<br />
<br />
[[SPG Agenda July 12 2011|Agenda]]<br />
<br />
==ISO Data Quality *==<br />
Standardizing the myriad of ways in which data quality can be measured is a very difficult and maybe even impossible task. Rather than taking this on, the ISO Metadata Standards provide the capability for describing data quality measures, how those measures are applied to a resource and what the results are. These approaches will be demonstrated along with connections between ISO and other dialects.<br />
<br />
==Preservation and Stewardship Use Case Workshop==<br />
In this session, we will refine and elaborate various scenarios in the life cycle of earth science data. We are taking two approaches -- First, trying to categorize and explore the breadth of scenarios, from individual scientists working and publishing themselves, to networks of citizen scientists, to industrial processing in large scale satellite missions. Second, we will select one or two and explore them in great detail throughout the life cycle.<br />
From these scenarios, we will extract the requirements for the other requirements: identifiers, citations, provenance and context content standard, ontology, etc.<br />
<br />
==Preservation and Stewardship Cluster Planning Breakout==<br />
We will review a brief status of the various active activities in the cluster and discuss future plans and milestones for the cluster. Those activities include: Data Stewardship Principles, Identifiers, Citations, Provenance and Context Content Standard, and Preservation Ontology.<br />
<br />
==Provenance and Context Content Standard Breakout==<br />
The purpose of the session is to discuss progress made in developing the Provenance and Context Content Standard proposed during the Winter meeting. Following a brief status presentation, the content items developed so far will be discussed in detail. Inputs will be solicited from the group regarding content items, their representation, and their appropriateness/adequacy to satisfy the needs of future users. Also, next steps in the standard development process will be identified.<br />
<br />
==Citations Breakout==<br />
"We will review recent advancements and the state of the art in citations, including a review of the GeoData 2011 meeting and GEOSS Science and Tech Committee citations standards.<br />
<br />
We will also have a ""citation writing workshop"" -- bring your data set and we'll help you figure out how to cite it. This may also contribute to our understanding of more difficult citation needs that we will need to explore.<br />
<br />
==Preservation Ontology Breakout ==<br />
A joint session across the Semantic Web and Preservation and Stewardship Clusters aimed at applying the semantic web technologies to the interoperability needs of preservation and stewardship. We will start with a brief presentation on the high-level steps of ontology engineering, which typically begins with forming use cases and "concept mapping". We will also briefly cover some popular provenance models (e.g. Open Provenance Model) and ISO metadata standards. The session will then focus on the initial steps of "concept mapping" some of the use cases from the Provenance and Context Content Standard. Come see some "sausage making" as we do some concept maps.<br />
<br />
== IQ cluster ==<br />
The IQ Cluster will begin its work to understand different quality needs as presented by different science domain communities. These presentations will inform the development of a quality framework that might be broadly applied to the Earth science data and information community. In addition, these presentations will assist in the ESIP Federation's contributions to the GEO Quality Assurance for Earth Observations (QA4EO) task, as led by CEOS' Working Group on Calibration and Validation. The IQ Cluster also will hear from the Semantic Web Cluster to develop a quality ontology.<br />
<br />
===1st session (July 14, 1:30-3:00)===<br />
:Intro and welcome – Greg Leptoukh (15 minutes) <br />
:QA4EO Overview – Greg Stensaas (15 minutes) <br />
:NASA Perspective on Data Quality – Frank Lindsay (15 minutes) <br />
:Semantic Technologies for Data Quality – Chris Lynnes or Peter Fox (45 minutes)<br />
<br />
===2nd session (July 14, 3:30-5:00)===<br />
:Data Quality Needs and Approaches from Different Communities (60 minutes)<br />
::*George Huffman (precipitation) <br />
::*Kerstin Lehnert (geochemistry?) <br />
::*Ed Armstrong (sea surface temperature) <br />
::*Ross Bagwell? (air quality) <br />
:Data Quality Standards<br />
::*Ted Habermann (ISO) (15 minutes) <br />
::*Barry Weiss (15 minutes)<br />
<br />
===3rd session (July 15, 1:00-2:30)===<br />
:Business Meeting<br />
::*Selection of co-chair<br />
::*Discussion of next steps<br />
<br />
=== Other Quality Sessions ===<br />
* AQ will have a panel discussion (Th- 10:30-12)<br />
<br />
==Global Change Master Directory (GCMD) Metadata Authoring Workshop == <br />
NASA's Global Change Master Directory (GCMD) enables users to discover and access data, services, and climate visualizations relevant to global change and Earth science research. In this session, participants will learn about the value of the GCMD for discovering Earth science data, services, and visualizations. In addition, data and services from ESIP members will be highlighted in the updated ESIP portal. A "hands-on" demonstration of our metadata authoring tool will be given and participants will have the opportunity to use the tool for describing their data, services, and visualizations. Please bring your laptop to the workshop.<br />
<br />
[http://gcmd.nasa.gov/ GCMD Website]<br />
<br />
[http://gcmd.nasa.gov/User/authoring.html Metadata Authoring Tool]<br />
<br />
== CF Standards Extensions for Remote Sensing Data ==<br />
The CF metadata conventions were developed originally to meet the needs of the modeling community. We will discuss extensions needed to serve the needs of the remote sensing community, including: spectral band descriptions, swath geometry representation, and data quality representations. If there is sufficient interest, we will form a new Cluster to address these topics.<br />
<br />
&nbsp;<br />
<hr><br />
<br />
=Information Technology and Interoperability=<br />
<br />
== Science on Drupal == <br />
* Intro to drupal on various levels <br />
* Show and tell <br />
* BoF sessions<br />
<br />
==ESIP Discovery Show and Tell==<br />
We will begin with a brief overview of the technologies in the ESIP Discovery Cluster. Then we will demo several actual implementations with a little discussion of what it takes to put an implementation together.<br />
* 8:30-8:45 Overview of the Discovery Cluster (C. Lynnes) <br />
* 8:45-9:00 NSIDC (Ruth Duerr) <br />
I will be demonstrating our live service, collection, and data cast feeds, the ability to aggregate feeds from multiple sources and serve them out again, as well as a portal that is totally service driven - in other words it uses OpenSearch to find the data sets that it advertises, OpenSearch to find granules of those data sets, etc. With luck you'll be able to subscribe to the results of a spatial/temporal/keyword query against the aggregator; but I am not counting on that (the iteration that functionality should be completed in starts next week!).<br />
* 9:00-9:15 JPL (Andy Bingham) <br />
* 9:15-9:30 EOS Clearinghouse (Matt Cechini <br />
The Earth Observing System Clearinghouse (ECHO) has historically provided<br />
a SOAP-based programmatic interface to its metadata holdings. The SOAP<br />
interface provided a full-featured set of capabilities, but the nature of<br />
SOAP/WSDL communication required a moderate level of programming<br />
experience and effort when building an ECHO client application. The ECHO<br />
team, in cooperation with the ESIP Discovery cluster, developed the<br />
lighter weight OpenSearch API, layering it on top of its SOAP API as a<br />
simplified means of access. The new API immediately opened ECHO up to<br />
numerous new client partners and provided a simpler response format for<br />
internal use. These opportunities and the additional uses of the<br />
OpenSearch response format will be discussed.<br />
* 9:30 - 9:45 Eric Rozell<br />
I will talk about integrating semantics with OpenSearch. I'll show<br />
a demo of a faceted browser that we've developed for BCO-DMO based on the <br />
OpenSearch interface and an OWL vocabulary that describes some of the<br />
URIs that can be embedded in OpenSearch. In particular, I'll talk about<br />
the "rel" attribute and how it can be used for coupling services with UIs <br />
and applications, and also how it can be used to add more service<br />
execution details (outputs, preconditions, effects). I'll also talk a<br />
little about parameter extensions. Lastly, I'll talk about how we hope<br />
to use the OWL vocabulary as a web service abstraction that can<br />
integrate/federate across standards beyond OpenSearch.<br />
* 9:45-10:00 Chris Lynnes or Ken Keiser (TBD)<br />
<br />
==Earth Science Collaboratory==<br />
This session will convene the Earth Science Collaboratory. The main topic will be how to move forward with ESC, generate and maintain momentum, and actually put something together:<br />
* Intro/Recap of ESC Concept (Lynnes)<br />
* [[ESC Stories]]<br />
* [[ESC Implementation Strategies]]<br />
<br />
== Limitations in the exposure of earth science metadata via THREDDS and OPeNDAP servers==<br />
Earth data records are increasingly being made accessible via OPeNDAP and/or THREDDS data servers allowing client software to transparently access huge quantities of data. However, the organization, and quality and quantity of metadata that accompany a data collection or individual granules exposed via THREDDS and OPeNDAP can vary dramatically. For a user a priori familiar with the contents and structure of existing data products including variable names, descriptions, scaling factors, units etc this is not a problem since the fields available are enough on convey meaning. In contrast, to an application that crawls a THREDDS/OPeNDAP repository for meaningful metadata or even a data mining application, the quality of metadata available is supremely critical. For example, if variable names do not follow conventions like CF, it is difficult to automatically crawl a repository and understand the geophysical nature of data available. In this session we will explore these issues and review some practical examples as well as explore some best practices that could implemented. <br />
<br />
==Products and Services Committee Testbed Activities==<br />
Session would include an overview of the status and activities of the Products and Services Committee's Testbed. Individual Testbed developers would be asked to present overviews on their activities.<br />
<br />
==Open Source Software in the Sciences==<br />
"This session would involve talks and a panel discussion on leveraging open source software in the sciences. Important issues to cover:<br />
<br />
* What are the emerging and important open source technologies being used in the sciences?<br />
* What are the licensing issues with using open source software?<br />
* What open source software communities should ESIP be targetting?<br />
* How can we set up successful open source software communities?<br />
* What are the concerns in the areas of redistribution, attribution and commercialization that we should care about when dealing with open source software?<br />
* How does the use of open source affect your system's architecture?<br />
* What are the successful open source models?<br />
<br />
We will invite members from the ESIP community to come and weigh in on the above topics, as well as have a focused panel with some directed questions that help to flush out some of the ideas and topics.<br />
<br />
==Visualization Practices==<br />
We all use visualization to show the results of our data -- graphs, maps, interactive applications, etc. How do we decide what gets visualized and how do we go about that process to meet the needs of our target audiences? This breakout will feature case studies illustrating these practices from a variety of data providers and visualizers.<br />
<br />
==Technology Infusion for the Decadal Survey Era: Data Quality Capability Needs==<br />
Based on information derived from the NASA Technology Infusion Working Group's decadal survey mission use cases, this session will explore candidate technologies and infusion strategies that could be applied to meet the technology needs of data systems for the decadal survey era missions. <br />
<br />
The focus at ESIP will be three key challenges arising from the use cases that relate to Data Quality:<br />
# How to communicate a clear, consistent, coherent model / terminology for Data Quality to the user community<br />
# How to develop a community consensus on the quality of datasets<br />
# Assessing the quality of custom data products<br />
<br />
==Service Casting ==<br />
<br />
==Semantic Web Planning==<br />
* Summarize activities of previous 6 months<br />
* Plan for January meeting (likely topic: collaboration)<br />
* Plan for activities in the meantime<br />
* Consider Erin's Use Case for the Projects ontology<br />
<br />
=Cloud Computing = <br />
==Intro to Cloud Computing==<br />
As a complement to the proposed Cloud Computing workshop, this session will be aimed at those new to the concept, principles, and Federal mandate. CC will be defined and explained in basic technical terms. Roles will discussed, such as that of the system owner, the system integrator, and the hosting provider. A list of pros and cons--with examples--will be offered along with the identification of some of the key players in the marketplace. <br />
<br />
Beyond this management and technical overview, a brief review of the Office of Management and Budget's 'Cloud First' policy will be presented along with some analysis as to how that fits with data center consolidation.<br />
<br />
==Cloud Computing Workshop: Hands-On==<br />
This session is a hands-on workshop to help Earth scientists experience the process of deploying applications on a commercial cloud platform. We will use the Microsoft Azure Cloud as an example. Microsoft has agreed to make free Azure accounts available for the participants of this session. The participants will be able to register for a free cloud account before the workshop. The presenters will first show how to deploy two geospatial Web applications on the Azure cloud platform. These applications are: (i) Digital Elevation Model (DEM) interpolation and (ii) an instance of the open layer geospatial viewer. In the second part, the presenters will (optionally) help the participants deploy their own application(s) using their free Azure account. The presenters will assume moderate technical background, and the tutorial is designed for a large audience with various backgrounds. If you are attending this session, please subscribe to the ESIP_2011_Cloud list by visiting this link: <br />
<br />
http://cisg.gmu.edu/mailman/listinfo/esip_cloud<br />
<br />
You will then be able to receive emails regarding the session's logistics. <br />
<br />
Thanks.<br />
<br />
==Cloud Computing Applications and Studies==<br />
This session focuses on the applications and studies of cloud computing. In recent years, there has been a lot of interest on understating and apply cloud computing in Earth Science, in areas such as science data processing, user supports, decision support, just to name a few. Representatives from several NASA-funded projects have been invited to share their experience.<br />
<br />
* Evaluating Cloud Computing in the NASA DESDynI Ground Data System - John Tran - NASA/JPL<br />
* The Airborne Cloud Computing Environment (ACCE) Project - Sean Hardman - NASA/JPL<br />
* Oceanographic Cloud Study - Michael Gangl - NASA/ESDIS/PO.DAAC<br />
* The Lunar Mapping and Modeling Project (LMMP) - Emily Law - NASA/JPL<br />
* Geospatial Platform Demo: A cloud study using EC2 and Azure - Phil Yang - GMU<br />
<br />
==Cloud Computing for Earth Science Panel Discussion==<br />
Based on recent advancement in cloud computing, and the needs for cloud computing from agencies, industry, academia in enabling research and applications, we organize the panel among agencies, academia, industry to discuss how cloud computing could help Earth sciences. We will discuss:<br />
1. How to put Earth science applications onto Cloud Computing environment?<br />
2. Why we need cloud computing for Earth sciences and what can't be achived without cloud computing?<br />
3. How to optimize application or cloud computing to enable Earth science and applications? <br />
4. How the Earth science and applications may shape cloud computing? <br />
<br />
<hr><br />
<br />
=Societal Benefit Areas and Education/Outreach=<br />
==Teacher Workshop ==<br />
Participating G6-12 educators will attend a 1.5 day workshop that starts Tuesday morning and wraps up Wednesday at noon. The teacher workshop will have an overall theme of Earth Science Education with an integral strand dedicated to Climate Change Education where educators will learn about climate change science, climate resources, and ways to effectively communicate climate change topics.<br />
<br />
Educators will also be able to choose from several breakout sessions demonstrating ways that Earth science tools and data can be used in science classrooms. Workshop sessions will be led by ESIP members from NOAA, NASA, EPA, DOE, and several Universities from around the country. Educators will also have a chance to brainstorm lesson plan development based on grade levels. After lunch, everyone is invited to stay for the ESIP conference plenary sessions followed by a fun and informational poster session Wednesday evening.<br />
<br />
For more details:<br />
<br />
visit http://cimss.ssec.wisc.edu/teacherworkshop/esip/ <br />
<br />
or<br />
<br />
[[Media:Agenda&TeacherTrackSessionsESIP 2011.pdf|download a PDF version of the workshop agenda]].<br />
<br />
=== Presentation Files ===<br />
<br />
[[Media:BenedictTeacherWorkshop.pdf|PDF version of Karl Benedict's Workshop entitled "Finding and using map and data services for data intensive science teaching"]]<br />
<br />
==Broader Impact: Expert Science Review of Educational Materials==<br />
<br />
The Climate Literacy and Energy Awareness Network (CLEAN) Pathway project invites you to contribute your scientific expertise to educators by providing the final expert review of climate change and energy resources before they are accepted into the collection.<br />
<br />
'''You can provide your review right at the meeting using our online review station.''' The location of the review station will be posted here soon.<br />
<br />
CLEAN's primary goal is to steward a broad collection of educational resources and foster a supporting community to help facilitate students, teachers, and citizens becoming climate literate and informed about "the climate's influence on you and society and your influence on climate." The current collection can be explored at http://cleanet.org.<br />
<br />
&nbsp;<br />
<hr><br />
<br />
<br />
== Energy and Climate Cluster ==<br />
<br />
July 13, 2011 Wednesday <br />
<br />
8:15 – 9:45 AM Track 5 Energy-Climate Breakout<br />
<br />
* GEOSS Architecture Implementation Pilot (AIP-3) Energy Scenario: Use case of the environmental impact assessment of the production, transportation and use of energy for the photovoltaic (PV) sector – Lionel Menard, École des Mines de Paris (via WebEx)<br />
* Wind Energy Resource Assessment – Daran Rife, NCAR<br />
* Application of Statistical Correlations of Sub-Hourly Irradiance Measurements and Hourly SUNY Data to Photovoltaic Array Performance – Marissa R. Hummon, National Renewable Energy Laboratory<br />
<br />
9:45 – 10:00 AM Break<br />
<br />
10:00 AM – 12:00 PM Track 5 Energy-Climate Breakout (Cont’d)<br />
<br />
* Partnerships for Wind Energy Siting Decision Tools – Alison LaBonte, OSTP, and Taber Allison, AWWI (via WebEx)<br />
* NREL Data Sources and Quality – Debbie Brodt-Giles, National Renewable Energy Laboratory (via WebEx)<br />
* The New Peer-To-Peer Architecture of the Earth System Grid Federation – Luca Cinquini, NASA/JPL<br />
* Impact of Climate Change on Energy Demand and the Optimal Site Selection of Wind and Solar Farms - Glenn Higgins et al, Northrop Grumman<br />
<br />
July 15, 2011 Friday <br />
<br />
8:30 – 10:00 AM Track 5 Energy-Climate Breakout<br />
<br />
* ESIP Energy-Climate Cluster - A Project Proposal - "Wind Energy Siting Data Coordination"<br />
<br />
== Air Quality Work Group ==<br />
* Interoperability workshop <br />
* Panel on AQ Data Quality Needs<br />
<br />
<br />
<hr><br />
=Organizational=<br />
==Proposed Bylaw Changes: ESIP Community Discussion ==<br />
http://wiki.esipfed.org/index.php/Constitution_and_Bylaws#Proposed_Bylaw_Changes<br />
<br />
== Building and Leveraging Capacities for the ESIP Community ==<br />
As an organization, ESIP optimizes collaboration and fostering connections through in-person meetings and virtually through collaboration space on the Web. The networked, community-driven approach largely is aimed at fostering Earth science interoperability – for data, systems, people and organizations. This synergy between collaboration and broad expertise allows the ESIP Federation to play an important coordination role for the Earth science data and technology community. The ESIP Federation is fostering the development of a research community that cuts across traditional discipline and related boundaries, enabling communities to share tools, data and technology. Ultimately, this coordination across sectors and communities will address problems central to access and use of Earth science data and information, allow Earth science research to be of higher quality and done more quickly, and leverage the work of the many communities contributing to Earth science knowledge. The ESIP Federation is at a strategic crossroads with the development of these important opportunities. This breakout session will focus on discussion about how the Federation can build and leverage collaboration capabilities in order to move forward successfully. There will also be time to discuss how to leverage ESIP’s on-going contributions to the current community while providing an open and welcoming space for external organizations to join forces. Please come and share your ideas and vision about how ESIP should move forward and work with others.<br />
<br />
== ESIP 101 == <br />
As the ESIP Federation has grown in size and scope of activities, many new faces have been drawn into our community. For those new to the ESIP Federation or anyone interested in learning more about its activities, join us for an overview presentation that will highlight the history, current activities, opportunities for involvement and how to become a partner. Bring your morning joe and breakfast to this informal session.</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=File:BenedictTeacherWorkshop.pdf&diff=33797File:BenedictTeacherWorkshop.pdf2011-07-12T12:26:03Z<p>Kbene: Presentation prepared by Karl Benedict for the ESIP Summer Meeting 2011 Teacher Workshop.</p>
<hr />
<div>Presentation prepared by Karl Benedict for the ESIP Summer Meeting 2011 Teacher Workshop.</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Pub_crawl_info&diff=33794Pub crawl info2011-07-11T20:18:21Z<p>Kbene: </p>
<hr />
<div>== Santa Fe Pub Crawl Venue Information ==<br />
<br />
=== Where & When ===<br />
Tuesday, July 12<br />
<br />
7:00 PM<br />
<br />
La Fonda Lobby, near the Registration Desk<br />
<br />
=== Links===<br />
<br />
Twitter: [http://twitter.com/#!/search/realtime/%23esipcrawl #esipcrawl]<br />
<br />
[http://tinyurl.com/6j82scu Interactive Map ]<br />
<br />
[[Media: ESIPpubCrawl.pdf | PDF version of pub crawl information]]<br />
<br />
=== Map & Venue Descriptions===<br />
<br />
[[File: esipcrawl.png| 600px]]<br />
<br />
====Marble Brewery Taproom====<br />
Nice upstairs pub with NM brewed beers, pizzas, and a large outdoor terrace. On the upper floor, overlooking the Santa Fe Plaza.<br />
<br />
====San Francisco St. Grill and Bar====<br />
Somewhat small bar area with good margaritas, mixed drinks, and 5 beers on tap. Large dining area with broad “American” style menu. <br />
<br />
====Sleeping Dog Tavern====<br />
Pub with good selection of local and imported beers, mixed drinks & bar menu. Their white chile is excellent. Located below street level off of San Francisco St.<br />
<br />
====Blue Corn Cafe and Brewery====<br />
Large New Mexico restaurant with their bar at the back of the restaurant. Good locally brewed beers and an excellent selection of tequilas. Located upstairs. <br />
<br />
====Coyote Cantina====<br />
Nice upstairs open-air bar with a focus on mixed drinks (they make an excellent coco loco from their own pineapple infused rum) and a bit of a “beach” vibe. Excellent guacamole and house-made chips. <br />
<br />
====Del Charro Bar====<br />
Nice bar off further off the plaza with more of a “local” feel. Good selection of beers and mixed drinks. Great margaritas. They have a back room that can accommodate a larger group if needed.</div>Kbenehttps://wiki.esipfed.org/w/index.php?title=Pub_crawl_info&diff=33793Pub crawl info2011-07-11T19:44:45Z<p>Kbene: </p>
<hr />
<div>== Santa Fe Pub Crawl Venue Information ==<br />
<br />
Twitter: [http://twitter.com/#!/search/realtime/%23esipcrawl #esipcrawl]<br />
<br />
[http://tinyurl.com/6j82scu Interactive Map ]<br />
<br />
[[Media: ESIPpubCrawl.pdf | PDF version of pub crawl information]]<br />
<br />
[[File: esipcrawl.png]]<br />
<br />
===Marble Brewery Taproom===<br />
Nice upstairs pub with NM brewed beers, pizzas, and a large outdoor terrace. On the upper floor, overlooking the Santa Fe Plaza.<br />
<br />
===San Francisco St. Grill and Bar===<br />
Somewhat small bar area with good margaritas, mixed drinks, and 5 beers on tap. Large dining area with broad “American” style menu. <br />
<br />
===Sleeping Dog Tavern===<br />
Pub with good selection of local and imported beers, mixed drinks & bar menu. Their white chile is excellent. Located below street level off of San Francisco St.<br />
<br />
===Blue Corn Cafe and Brewery===<br />
Large New Mexico restaurant with their bar at the back of the restaurant. Good locally brewed beers and an excellent selection of tequilas. Located upstairs. <br />
<br />
===Coyote Cantina===<br />
Nice upstairs open-air bar with a focus on mixed drinks (they make an excellent coco loco from their own pineapple infused rum) and a bit of a “beach” vibe. Excellent guacamole and house-made chips. <br />
<br />
===Del Charro Bar===<br />
Nice bar off further off the plaza with more of a “local” feel. Good selection of beers and mixed drinks. Great margaritas. They have a back room that can accommodate a larger group if needed.</div>Kbene