Minimally maintained

Apache Solr module helps you to integrate the ApacheSolr to Drupal, but this module doesn't include all CCK Fields.

Here are 2 HOOKs to add your custom fields to Apachesolr,

1. HOOK_apachesolr_cck_fields_alter
arguments: &$mappings,
add your field_name to this array, and return.

$mapping[‘per-field’][$field_name] =array('callback' => '', 'index_type' => 'string');

2. HOOK_apachesolr_update_index
arugments: $document, $node, $namespace.
so you can add any field to the $document.

Use Apachesolr Custom Fields to get out of any custom code to do this, what you need to is go to administration page and add some settings to determine which field need to be indexed or not.

The mechanism is to store all cck fields settings into database, and add your custom fields settings into database also.
Further more, this module convert those 2 hooks into the same one, and the same interface.
When you go to the page, index.php?admin/settings/apachesolr/custom-fields, there is a list of cck fields, and a link you can add your custom field. Go each field settings page on the page, you will get a page which contains more description on the page.

Apache Solr Indexing Mechanism

Developer Blocks allows a developer to:

Adds random 'did you know?' messages in the help region for administrators, on non-admin pages. The messages themselves are stored in the install file, and are transferred to the database when you install or update.

As it is, the only way to turn it off is to disable the module, which is instructive in and of itself. It shows random helpful 'knowables,' and is hard-coded to link to a path on drupal.org.

Needs a test. Also: Contextual menu/link that takes the user to a page with an explanation of how to turn the thing off. Perhaps something like hook_knowable_info(). And... Looking over the code now I realize I used t() instead of st() for the knowables file loaded by hook_install().

From the include:

What is a 'knowable?' A knowable is a short statement that introduces a user to a topic in a general way.

The main text should be two sentences or less. The first sentence is a broad statement regarding the topic. The second sentence explains how to achieve the topic goal.

Following these two sentences is a link to a page on drupal.org which presents a more in-depth discussion of the issue. This link has two components: The link target, as a relative path to drupal.org, and the text that is linked.

Example: "Drupal can be extended with modules and themes. These can be downloaded from drupal.org, and endabled on the Modules administration
page."

Custom module for importing data.

Turns out this module is a duplicate of Admin Select, which also has a D6 release. So please use that module instead.

If you have ever faced the problem of adding extra information to a nodereference, e. g. an amount, tag or booking information, there hasn't been an easy solution yet.