POC Conf. Call 10-4-11 - Revision history

Cooperl at 19:40, 8 March 2012

2012-03-08T19:40:44Z

Cooperl: /* Updating of Dbxrefs */

2011-10-22T19:51:22Z

Updating of Dbxrefs

Cooperl: /* Issues and status reports for the Upcoming Release */

2011-10-11T19:25:14Z

Issues and status reports for the Upcoming Release

Cooperl: /* Timeline of Upcoming Release */

2011-10-07T20:28:11Z

Timeline of Upcoming Release

Cooperl: /* Timeline of Upcoming Release */

2011-10-07T19:51:53Z

Timeline of Upcoming Release

Cooperl: /* Grape */

2011-10-07T19:00:12Z

Grape

Cooperl at 18:24, 6 October 2011

2011-10-06T18:24:13Z

Cooperl: /* Botany 2012 */

2011-10-05T20:51:31Z

Botany 2012

Cooperl: /* PAG 2012 */

2011-10-05T16:02:05Z

PAG 2012

Cooperl at 16:00, 5 October 2011

2011-10-05T16:00:56Z

@@ Line 6: / Line 6: @@
 Absent: '' Dennis Stevenson (NYBG),  Barry Smith (University at Buffalo, NY), Chris Mungall (Lawrence Berkeley National Lab)''
 Collaborators: none
 Any changes or corrections (additions/deletions, etc) needed in the minutes from the [[POC_Conf._Call_9-27-11]]?''There were no additions, deletions, or changes''

← Older revision		Revision as of 19:51, 22 October 2011
Line 191:		Line 191:

	For example see: [http://beta.plantontology.org:8080/amigo/go.cgi?view=details&search_constraint=terms&depth=0&query=PO:0030027&session_id=4455b1317680172 thallus (PO:0030027)] working on beta browser		For example see: [http://beta.plantontology.org:8080/amigo/go.cgi?view=details&search_constraint=terms&depth=0&query=PO:0030027&session_id=4455b1317680172 thallus (PO:0030027)] working on beta browser
−
−
−
−

	==Annotation files==		==Annotation files==

@@ Line 15: / Line 15: @@
 =Issues and status reports for the Upcoming Release=
-For more details of the changes in the upcoming release,  see: [[Summary of Changes to PO September 2011]]
+For more details of the changes in the upcoming release,  see: [[Summary of Changes to PO October 2011]]
 ==Timeline of Upcoming Release==

@@ Line 21: / Line 21: @@
 After today's edits to palea and lemma, the plant_ontology.obo file will be considered complete for this release, barring any major issues that are noticed.
-''Once that is done, we send out a notice to our collaborators and ask them to update the annotation files.  This involves asking TAIR to suspend their automatic script that runs on a weekly basis, as they have to access the dev version of the ontology file, not the live one.  Usually, we give the database groups about a week to update the files on their end and often this entails LC and JE just looks after making the required changes. ''
+''Once that is done, we send out a notice to our collaborators and ask them to update the annotation files.  This involves asking TAIR to suspend their automatic script that runs on a weekly basis, as they have to access the dev version of the ontology file, not the live one.  Usually, we give the database groups about a week to update the files on their end. ''
-''Note added after the meeting:  We will not be asking all the groups to amend their files with the col 16 annotations and add the extra lines at this point, but will start doing this for the next release''
+'''''Note added after the meeting:'''  We will not be asking all the groups to amend their files with the col 16 annotations and add the extra lines at this point, but will start doing this for the next release''
 ''We discussed the option of proceeding in a two-stage release where the "finished" plant_ontology.obo file is loaded onto the live browser. We will run the QC checks on annotation files (check for obsoletes and column 16 annotations) and then we send out a notice to the database groups that they need to update their files.  Once the new files come in they will be uploaded to the database.''

← Older revision		Revision as of 19:51, 7 October 2011
Line 22:		Line 22:

	''Once that is done, we send out a notice to our collaborators and ask them to update the annotation files. This involves asking TAIR to suspend their automatic script that runs on a weekly basis, as they have to access the dev version of the ontology file, not the live one. Usually, we give the database groups about a week to update the files on their end and often this entails LC and JE just looks after making the required changes. ''		''Once that is done, we send out a notice to our collaborators and ask them to update the annotation files. This involves asking TAIR to suspend their automatic script that runs on a weekly basis, as they have to access the dev version of the ontology file, not the live one. Usually, we give the database groups about a week to update the files on their end and often this entails LC and JE just looks after making the required changes. ''
		+
		+	''Note added after the meeting: We will not be asking all the groups to amend their files with the col 16 annotations and add the extra lines at this point, but will start doing this for the next release''

	''We discussed the option of proceeding in a two-stage release where the "finished" plant_ontology.obo file is loaded onto the live browser. We will run the QC checks on annotation files (check for obsoletes and column 16 annotations) and then we send out a notice to the database groups that they need to update their files. Once the new files come in they will be uploaded to the database.''		''We discussed the option of proceeding in a two-stage release where the "finished" plant_ontology.obo file is loaded onto the live browser. We will run the QC checks on annotation files (check for obsoletes and column 16 annotations) and then we send out a notice to the database groups that they need to update their files. Once the new files come in they will be uploaded to the database.''

@@ Line 253: / Line 253: @@
 At last week's meeting, [POC_Conf._Call_9-27-11]  we decided that we will not try to include these in this release, but will continue building it.  Column 1. DB reference should be to CRIBI (sp?) link?.  PJ will talk to PlexDB to get the microarray expression data- PlexDB has ~17 grape experiments, so we could link to m/a probe ids mapped to the genes. Julie Dickerson may be able to send us a dump for the database.
-  ''Today, the decision was to include this information''  Did I catch this correctly?
+''We decided last week to include this information in the next release, but will continue to work wiht the folks at CRIBI to get it in shape.  LC will contact Nicola there and work on updating and combining the files ''
 ==Final edits to be fixed:==

← Older revision		Revision as of 18:24, 6 October 2011
Line 11:		Line 11:


−	Any changes or corrections(additions/deletions, etc) needed in the minutes from the [[POC_Conf._Call_9-27-11]]?''There were no additions, deletions, or changes''	+	Any changes or corrections (additions/deletions, etc) needed in the minutes from the [[POC_Conf._Call_9-27-11]]?''There were no additions, deletions, or changes''

← Older revision		Revision as of 20:51, 5 October 2011
Line 433:		Line 433:
	• A Rotating Banner Ad on the 2012 Conference Registration site.		• A Rotating Banner Ad on the 2012 Conference Registration site.

−	''PJ will check with Gramene and ~~xxxx~~ to see if they want to co-host a booth.''	+	''PJ will check with Gramene and Doreen Ware to see if they want to co-host a booth.''

@@ Line 323: / Line 323: @@
 ''Should have talks from people working on ontology applications, rather than ontology development, to show utility.''
-''PJ suggested the following:  Text mining applications like TextPresso, Phenolog, others...?''
+''PJ suggested the following:  Text mining applications like TextPresso, Phenolog, Nick Provart (BAR) others...?''
 ''Procedure:  LC should contact potential speakers and ask them to submit an abstract to us and to the organizers.''

← Older revision		Revision as of 16:00, 5 October 2011
Line 11:		Line 11:


−	Any changes or corrections(additions/deletions, etc) needed in the minutes from the [[POC_Conf._Call_9-27-11]]?	+	Any changes or corrections(additions/deletions, etc) needed in the minutes from the [[POC_Conf._Call_9-27-11]]?''There were no additions, deletions, or changes''