Differences

This shows you the differences between two versions of the page.

--- 4dn:phase1:working_groups:policy:february-2016-notes [2019/02/15 15:45]
rcalandrelli created
+++ 4dn:phase1:working_groups:policy:february-2016-notes [2025/04/22 16:21] (current)
@@ Line 14: / Line 14: @@
 Absent: Iddil Bekirov, Stephanie Alexander
-.\__Frequency of meetings.  Requests coming in for manuscript submissions to DCIC creates some urgency for our business.  Encode policy to serve as a basis for our policy in three areas: data release, publications, software.
+.\__Frequency of meetings. Requests coming in for manuscript submissions to DCIC creates some urgency for our business. Encode policy to serve as a basis for our policy in three areas: data release, publications, software.
-a.\__Our next meeting will be March 14
+  * a.\__Our next meeting will be March 14
+  * b.\__Shoot for something to present to the steering committee in late March
-b.\__Shoot for something to present to the steering committee in late March
+.\__Tracking manuscripts to prevent conflicts and ID synergies. Nils has a draft policy document. Needs to be easy to upload, modify, track progress. Put abstract in initially, later full manuscript, update as it goes through publication. Options:
-.\__Tracking manuscripts to prevent conflicts and ID synergies.  Nils has a draft policy document.  Needs to be easy to upload, modify, track progress.  Put abstract in initially, later full manuscript, update as it goes through publication.  Options:
+  * a.\__Wiki—Contact OH if you do not have access.
+      * \__i. Nils ran us through the process of uploading a manuscript. Took about 5 min to fill in basic fields. Interested parties can subscribe to updates. File formats pdf. Searchable, keywords recommended. There is a field for comments on the abstract
+      * \__ii. When should something be uploaded? General agreement on time of manuscript submission.
+      * \__iii. What should be mandatory: Submitting author, title and abstract, at the time of manuscript submission. Other information is optional.
+  * b.\__Shared Google document—spreadsheet; not wieldy.
+  * c.\__GitHub—software for version control. Requires individual subscriptions. Deemed too complex.
+  * d.\__Decision to go with Wiki
+  * e.\__Means of enforcement? Will only be as good as people’s desire to participate, but not a high level of enthusiasm for formal sanctions beyond peer pressure.
-a.\__Wiki—Contact OH if you do not have access.
+.\__Data policy. Had decided at last meeting to start with Encode’s policy and modify as needed.
-\__i.     Nils ran us through the process of uploading a manuscript.  Took about 5 min to fill in basic fields.  Interested parties can subscribe to updates.  File formats pdf.  Searchable, keywords recommended.  There is a field for comments on the abstract
+  * a.\__Data should be released to consortium no later than when the manuscript is submitted. Will be released via DCIC.
+      * \__i. Submission earlier is OK and encouraged.
+      * \__ii. How do we protect this from being used undesirably, e.g. second party publishing before the first party?
+  * b.\__What data should be released? Omics yes. Discussion re imaging data. Decided that Nils will consult the other two working groups.
+  * c.\__Shankar raised issue of requirements for Common Fund program data release requirements. Latest time may be acceptance of first manuscript including data. General agreement that we can set earlier submission times but not go later.
+  * d.\__Software and source code should released for noncommercial use as well. Institutions may vary in how they handle commercial uses. To be dealt with at a later time.
-\__ii.     When should something be uploaded?  General agreement on time of manuscript submission.
+.\__Nils will work with Leonid to create a list of key points regarding data release. When should data be released and to whom? This will be sent around for email discussion.
-\__iii.     What should be mandatory: Submitting author, title and abstract, at the time of manuscript submission.  Other information is optional.
-b.\__Shared Google document—spreadsheet; not wieldy.
-c.\__GitHub—software for version control.  Requires individual subscriptions.  Deemed too complex.
-d.\__Decision to go with Wiki
-e.\__Means of enforcement?  Will only be as good as people’s desire to participate, but not a high level of enthusiasm for formal sanctions beyond peer pressure.
-.\__Data policy.  Had decided at last meeting to start with Encode’s policy and modify as needed.
-a.\__Data should be released to consortium no later than when the manuscript is submitted.  Will be released via DCIC.
-\__i.     Submission earlier is OK and encouraged.
-\__ii.     How do we protect this from being used undesirably, e.g. second party publishing before the first party?
-b.\__What data should be released?  Omics yes.  Discussion re imaging data.  Decided that Nils will consult the other two working groups.
-c.\__Shankar raised issue of requirements for Common Fund program data release requirements.  Latest time may be acceptance of first manuscript including data.  General agreement that we can set earlier submission times but not go later.
-d.\__Software and source code should released for noncommercial use as well.  Institutions may vary in how they handle commercial uses.  To be dealt with at a later time.
-.\__Nils will work with Leonid to create a list of key points regarding data release.  When should data be released and to whom?  This will be sent around for email discussion.
 </WRAP>~~TABLE_CELL_WRAP_STOP~~|

4D Nucleome Network Wiki

User Tools

Site Tools

Differences

Page Tools