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

Cooperl: /* Goals and Timeline for the next Release #18 */

2012-06-10T16:31:09Z

Goals and Timeline for the next Release #18

Cooperl: /* Update on the Release #17, April 2012 */

2012-06-10T16:30:17Z

Update on the Release #17, April 2012

Cooperl: /* Discussion of the PO Filenames */

2012-06-10T16:29:41Z

Discussion of the PO Filenames

Cooperl: /* Update on the Release #17, April 2012 */

2012-06-10T16:24:54Z

Update on the Release #17, April 2012

Cooperl: /* Update on the Release #17, April 2012 */

2012-06-10T16:21:22Z

Update on the Release #17, April 2012

Preecej: /* Plant Ontology Web Site and Browser Update: */

2012-06-01T20:10:58Z

Plant Ontology Web Site and Browser Update:

Cooperl: /* Demo - Integrating Annotated Images with PO terms */

2012-04-26T00:39:38Z

Demo - Integrating Annotated Images with PO terms

Cooperl: /* Demo - Integrating Annotated Images with PO terms */

2012-04-26T00:36:30Z

Demo - Integrating Annotated Images with PO terms

Cooperl: /* Demo - Integrating Annotated Images with PO terms */

2012-04-26T00:29:44Z

Demo - Integrating Annotated Images with PO terms

Cooperl: /* Demo - Integrating Annotated Images with PO terms */

2012-04-26T00:25:41Z

Demo - Integrating Annotated Images with PO terms

@@ Line 101: / Line 101: @@
 =Goals and Timeline for the next Release #18=
 Timeline:   End of june to Mid- July- '''before''' BSA and ASPB meetings?
 ''Agreed''

@@ Line 69: / Line 69: @@
 * Updates to the SOP page: [[PO_Release_SOP_Page]]
 ''Need to clarify where the various files go''
 * What do we need to do better next time?

@@ Line 78: / Line 78: @@
 ''We should follow up on running Oort to create the asserted version in the dev loading script- LC sent the link to JE  to run Oort on the command line''
 ==Discussion of the PO Filenames==
-Reason for having separate versions- we keep the editors version unasserted.
+Reason for having separate versions- we keep the editors version unasserted.  Relationships as that are asserted are based on what axioms are put in the file and those can change.
 editors version:- has inferred relations, then when we post it on AmiGO browser, we assert all the relations that have been inferred and call it po-asserted.
@@ Line 87: / Line 85: @@
 ''BS suggested that using "plant_ontology_assert" was misleading, and because this is the inferred file. RW pointed out that it was called "assert" based on the OboEdit function "assert implied links".''
-''BS: Users should see the file with inferred relations asserted (They do, since that is what is on AmiGO).''
+''BS: Users should see the file with inferred relations asserted: They do, since that is what is on the AmiGO browser on the PO site.''
-''We will look at the naming scheme that CM suggested (what GO uses) and see if that makes sense for PO.''
+''We will look at the naming scheme that CM suggested (what GO uses) and see if that makes sense for PO. Could change names if we do it carefully and document it''
 =Goals and Timeline for the next Release #18=

← Older revision		Revision as of 16:24, 10 June 2012
Line 77:		Line 77:

	''We should follow up on running Oort to create the asserted version in the dev loading script- LC sent the link to JE to run Oort on the command line''		''We should follow up on running Oort to create the asserted version in the dev loading script- LC sent the link to JE to run Oort on the command line''
		+	==Discussion of the PO Filenames==
		+	Reason for having separate versions- we keep the editors version unasserted.

		+	Relationships as that are asserted are based on what axioms are put in the file and those can change.
		+
		+	editors version:- has inferred relations, then when we post it on AmiGO browser, we assert all the relations that have been inferred and call it po-asserted.
		+
		+
	''BS suggested that using "plant_ontology_assert" was misleading, and because this is the inferred file. RW pointed out that it was called "assert" based on the OboEdit function "assert implied links".''		''BS suggested that using "plant_ontology_assert" was misleading, and because this is the inferred file. RW pointed out that it was called "assert" based on the OboEdit function "assert implied links".''

← Older revision		Revision as of 16:21, 10 June 2012
Line 75:		Line 75:

	''This is a good idea, although at this point, the creation of the asserted file cannot be done automatically and will have to be hand tweaked by the editors each time.''		''This is a good idea, although at this point, the creation of the asserted file cannot be done automatically and will have to be hand tweaked by the editors each time.''
		+
		+	''We should follow up on running Oort to create the asserted version in the dev loading script- LC sent the link to JE to run Oort on the command line''

	''BS suggested that using "plant_ontology_assert" was misleading, and because this is the inferred file. RW pointed out that it was called "assert" based on the OboEdit function "assert implied links".''		''BS suggested that using "plant_ontology_assert" was misleading, and because this is the inferred file. RW pointed out that it was called "assert" based on the OboEdit function "assert implied links".''

@@ Line 157: / Line 157: @@
 ==Plant Ontology Web Site and Browser Update:==
-Please see [[Plant_Ontology_Web_Site_Update:_Winter_2012]] for more details
+Please see [[Plant_Ontology_Web_Site_Update:_2012]] for more details
 *Items on the [http://palea.cgrb.oregonstate.edu/trac/report/1 tracker]:

@@ Line 44: / Line 44: @@
 ''Discussions about the options for linking to keywords and the level of curation needed: One approach is to link to keywords, but their def'n may or may not match our def'n, or the curate the images themselves.  May also mirror ale's images at OSU and those would be curated.  Could apply for curating other images such as the foxtail images.  Would be attributed back to source site.''
-''Desktop application could most likely be ready to demo for the workshop at the BSA meeting.  Will pull taxonomy terms from UBio''
+''Desktop application could most likely be ready to demo for the workshop at the BSA meeting.  Will pull taxonomy terms from UBio and could in the future pull terms from TO or GO. Database should be developed for fall.  Will plan to do another demo when Ale and KS can take part.  RW will coordinate it.  ''
 =Other notes about Images=

@@ Line 42: / Line 42: @@
 ''Pop-up (eg. shown above) would pull out any annotations to all images with that key words.''
-''Discussions about the options for linking to keywords and the level of curation needed: One approach is to link to keywords, but their def'n may or may not match our def'n, or the curate the images themselves.  May also mirror ale's images at OSU nad those would be curated.  Could apply for curating other images such as the foxtail images.  Would be attributed back to source site.''
+''Discussions about the options for linking to keywords and the level of curation needed: One approach is to link to keywords, but their def'n may or may not match our def'n, or the curate the images themselves.  May also mirror ale's images at OSU and those would be curated.  Could apply for curating other images such as the foxtail images.  Would be attributed back to source site.''
-''Desktop application could most likely be ready to demo for the workshop at the BSA meeting.''
+''Desktop application could most likely be ready to demo for the workshop at the BSA meeting.  Will pull taxonomy terms from UBio''
 =Other notes about Images=

← Older revision		Revision as of 00:29, 26 April 2012
Line 37:		Line 37:

	* Give the "secondary" annotation terms a more prominent location, perhaps on the left or right instead of the bottom.		* Give the "secondary" annotation terms a more prominent location, perhaps on the left or right instead of the bottom.
		+	* field for annotators on the desktop app, also can zoom on the segmentation tool.
		+	* Keeping things up to date- will not be an issue, as they will go through the webservices. All the parts will draw from from the database.

	''Pop-up (eg. shown above) would pull out any annotations to all images with that key words.''		''Pop-up (eg. shown above) would pull out any annotations to all images with that key words.''

← Older revision		Revision as of 00:25, 26 April 2012
Line 41:		Line 41:

	''Discussions about the options for linking to keywords and the level of curation needed: One approach is to link to keywords, but their def'n may or may not match our def'n, or the curate the images themselves. May also mirror ale's images at OSU nad those would be curated. Could apply for curating other images such as the foxtail images. Would be attributed back to source site.''		''Discussions about the options for linking to keywords and the level of curation needed: One approach is to link to keywords, but their def'n may or may not match our def'n, or the curate the images themselves. May also mirror ale's images at OSU nad those would be curated. Could apply for curating other images such as the foxtail images. Would be attributed back to source site.''
		+
		+	''Desktop application could most likely be ready to demo for the workshop at the BSA meeting.''

	=Other notes about Images=		=Other notes about Images=