Hyperlink references in anatomy term pages about vfb

[jefferis]

See also #188

[dosumis]

The relevant identifiers (FBrf) are in the latest file. Refs should all appear after the next FlyBase update.

[Robbie1977]

@dosumis Is that us/me pulling an update or flybase themselves?

[dosumis]

@mmc46 can advise when the next FB release will be. The refs will be there once VFB has loaded this release. For v.urgent additions it is possible to add to our local copy of FlyBase but the resulting hyperlinks won't work.

[mmc46]

The example shows refs that are already in FlyBase, but they're in a comment and have not been added to the definition, which means they don't get hyperlinked.
I'll need to find all cases of this and manually add them.
The next anatomy update will be on the 5th June.

[dosumis]

Looks like there are lots of new refs in the latest live ontology:

def: "The largest synaptic neuropil domain of the adult central complex, covered by an extensive glial sheath....." [FBC:BrainName, FlyBase:FBrf0049409, FlyBase:FBrf0205148, FlyBase:FBrf0210154, FlyBase:FBrf0212649, FlyBase:FBrf0213955...]

[mmc46]

Those were changes done before the last update on 2014-01-29. And these refs are in the fan-shaped body definition in /resources/fbbt-simple.owl (29-01-2014), so shouldn't they be showing up?

[dosumis]

Suggests to me that server is still running the old version of FlyBase.

[Robbie1977]

Main server is on FB2014_01, blanik is still on the old version as graham has been off sick and so replication isn’t running yet - wanted to use this as a test, hence leaving at old version.

I now see that you’ve released FB2014_02 so will run an update on blanik to test as haven’t run it unsupervised yet - takes nearly a day.

FYI The version is shown at the bottom of every page.

On 8 Apr 2014, at 17:38, David Osumi-Sutherland [email protected] wrote:

Suggests to me that server is still running the old version of FlyBase.

—
Reply to this email directly or view it on GitHub.

[Robbie1977]

Blanik update has been started 8/4 17:50.

Please Wait......

[Robbie1977]

@dosumis @mmc46 Database has been updated on blanik so the dev site. Can you check it looks right please.

[dosumis]

Looks good. @mmc46 & @Robbie1977 - perhaps worth co-ordinating DB & ontology updates via gcal. Would also be good to add ontology release ID to release info at bottom of page (probably need to make a new ticket for this). Then just need to develop a release ID system for the individuals file.

[Robbie1977]

We’re currently using the simple file OWLdate for this is there a better metric? - If so probably best to raise another ticket.

Is this ticket now done? also seem to be a few others that relate or are duplicates. Can these be closed if OK on dev now.

I’ll sort out updating Flybase on karenin if your happy with everything on dev?

On 10 Apr 2014, at 12:45, David Osumi-Sutherland [email protected] wrote:

Looks good. @mmc46 & @Robbie1977 - perhaps worth co-ordinating DB & ontology updates via gcal. Would also be good to add ontology release ID to release info at bottom of page (probably need to make a new ticket for this). Then just need to develop a release ID system for the individuals file.

—
Reply to this email directly or view it on GitHub.

[mmc46]

This ticket and #88 can be closed.
Everything seems fine on dev.

I've added the FB release and anatomy updates to the VFB calendar.

On 10 Apr 2014, at 14:06, Robbie1977 [email protected] wrote:

We’re currently using the simple file OWLdate for this is there a better metric? - If so probably best to raise another ticket.

Is this ticket now done? also seem to be a few others that relate or are duplicates. Can these be closed if OK on dev now.

I’ll sort out updating Flybase on karenin if your happy with everything on dev?

On 10 Apr 2014, at 12:45, David Osumi-Sutherland [email protected] wrote:

Looks good. @mmc46 & @Robbie1977 - perhaps worth co-ordinating DB & ontology updates via gcal. Would also be good to add ontology release ID to release info at bottom of page (probably need to make a new ticket for this). Then just need to develop a release ID system for the individuals file.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.