Complete

[Note-- "ODL" below should be read as OWL-DL or OWL DL, see http://www.w3.org/TR/owl-guide/ ]
See wikipedia FRBR

in SWAN
two manifestations related to one expression (work)

When we import the data from PubMed, it gives a reference to a documentation.

can create an expression even if only one manifestation-- but you do not have to.

The manifestation has all the metadata, the expression is just saying these two things are the same thing

Agaric knows that the best usability would never have people entering numeric IDs into a text field in the first place, but pending fancy remote search and completion techniques, we can at least take a set of numbers without rejecting them for using semicolons instead of commas.

hook_form_alter is my favorite hook, but it has a more specific and so cleaner variation in Drupal 6:

http://api.drupal.org/api/function/hook_form_FORM_ID_alter/6

Resolution

Exclude certain fields from Drupal search.

Agaric and Science Collaboration's real need for this is for AJAX autocompletion, the sort of function used to autocomplete taxonomy, userreference, and nodereferrence fields. It would be great not to have to create a custom indexing system each time you want autocomplete to act on certain fields.

So if you've found this you may as well get yourself a cookie now, in fact go and grab a whole box, and you can eat them in bed too, because after you read this your life will change.

Well, at least if you're trying to make WAMPServer run in Windows Vista

Enough talk, here is the crucial info you need, and as you read what is below and eventually get wamp working, know in your heart that you did it The Agaric Way...

Step 1 - find this file
C:\Windows\System32\drivers\etc\hosts

Step 2 - open it

Step 3 - eat a cookie, you deserve it

Science Collaboration Framework (SCF) has a "node proxy" module that allows Drupal to query a SPARQL endpoint and only loads the data when someone looks for it-- at this point it creates a node.

The system isn't bad and may be a good base lacking any established best practices in Drupal for lazy loading of nodes from outside data sources.

Ontology module in SCF profile's custom modules directory, originally authored by Mark Goetz, is very close to ready to be committed to Drupal.org. It relies on Taxonomy extra (taxonomy_extra) module, originally by Alister Lewis-Bowen, and also in SCF profile's custom modules.

Make the (presently undeclared) dependency on graphbrowser module optional.

Create a similar optional dependency on gene_ontology (or move both these additions of data out of the hack of being added on the theme layer).

Here is the new approach for importing a lot of taxonomy terms:

Parse the entire file into terms and their data.

Load existing terms by name or, preferably if available, a unique ID. Process these with individual taxonomy_term_save commands (enhanced to allow custom operations via a hook). This is a big for loop.

Here's a quick and easy way to make your clients cry tears of joy... Give them one click 'save to PDF' on any Drupal node

All you need is the print module, which you can find here --> http://drupal.org/project/print

While we prefer to use existing modules rather than create custom ones whenever possible, the specific needs for storing additional Gene Ontology data with Drupal (multiple kinds of relationships between terms) and the functionality of Term Fields module did not match up.

Furthermore, Term Fields: