Skip to content

Use this to add xrefs to metadata/db-xrefs.yaml and submit a pull request. Then they will be in the global xref file that AmiGO2 uses. Before making any changes, you need to update the fork to be consistent with the GO version. Use "git fetch upstream, git merge upstream/master, git push.

License

Notifications You must be signed in to change notification settings

Planteome/go-site-xrefs-fork

 
 

Repository files navigation

Stories in Ready Build Status

A collection of metadata, files, and tools associated with the GO public website and geneontology.org web presence.

As well, the tracker is used as a catch-all for anything not tied to another GO project.

Every directory should have its own description.

Any of the files here can be edited via the go-site page on github. After editing, create a pull request. Edits will be checked for validity by travis (see the .travis.yml file).

metadata

The location of all core GO-related metadata. Most notably:

  • db-xrefs.yaml - prefix registry, for anything that is col1 of a GAF, or the prefix of a CURIE/Identifier
  • users.yaml - metadata on GOC members and contributors
  • groups.yaml - metadata on GOC groups, for anything that cann be the value of a 'contributor' or 'assigned_by'
  • datasets/ - metadata on contributed and released files
  • rules/ - metadata on cGO annotation QC rules

Each of the these has their own yaml schema.

See the metadata/README.md for more details

scripts

Maintenance and support scripts.

drupal7

The files that we're using tp modify our Drupal 7 installation from stock. This may also serve as a base for when we push onto a service.

cgi-bin (legacy)

This files an scripts that we want to preserve from the old GO site. Ideally, any critical functionality can be rewritten in a simpler and more reusable way than the original.

About

Use this to add xrefs to metadata/db-xrefs.yaml and submit a pull request. Then they will be in the global xref file that AmiGO2 uses. Before making any changes, you need to update the fork to be consistent with the GO version. Use "git fetch upstream, git merge upstream/master, git push.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 69.6%
  • Python 18.5%
  • Perl 8.0%
  • HTML 1.7%
  • Makefile 0.8%
  • CSS 0.8%
  • Other 0.6%