Drupal Development

Special treatment will check where on the internet site visitors are coming from

What we do, is every time we leave a comment somewhere, that includes a link back to Agaric, we get that other sites' page's URI into the Related Content module.

Then when someone visits and we see the match, we say hello and offer up the content related to what they were just looking at! Instant custom landing page for everyone, organically.

Resolution

Time for us to get Form Tweak up on Drupal.org!

There are enough use cases, these modifications to "Save" (and the surprisingly frequent request to remove preview) to put the module out for others to use (and post endless feature requests against, heh).

I would like to store the variables in files rather than the variable table, though.

[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.

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).

In on use case, feeds as nodes (with FeedAPI) causes issues with dbscripts approach to managing staging and deployment. Dev and live will pull the same content with a different IDs. In one solution, we'll have to disable aggregation on development.

Do we have a module for that? "if at this address, force this module to disabled." Not that we can find.

It is a shame this isn't part of settings.php

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.