Overrides user login names with the LDAP DiplayName attribute, and optionally allows you to redirect to the Profiles website (http://profiles.web.cern.ch).

Uses

1. Forcing real names to update: In the administration interface, by selecting "Update real name" from the Update Options the real names for the selected users will be updated.
2. Changing path to the Profiles site: In the configuration settings interface, change the "Path to the default CERN Profiles site".

For developers and site builders

• Views: The real name and the CCID have been exposed to Views: if you need to include it in a view you can add it as a field, a filter or a contextual filter.
• Token: By enabling this module, the tokens will change: [user:name] will return the CERN Real name, while [user:name-raw] will return account name (NICE login name). You will also be able to access the CERN CCID for the user accounts.
• If you are writing PHP code, you can use the functions:
  1. format_username($account)
     Parameters: The account object for the user whose name is to be formatted. (ie. the user object for the user "stomanin")
     Return value: An unsanitized string with the name and surname for the provided account to display. (ie. Silvia Tomanin)
  2. cern_profiles_displayname_link_to_profiles_site($account_name)
     Parameters: The account name for the user whose name is to be formatted. (ie. stomanin)
     Return value: An unsanitized string with the name and surname for the provided account to display, linking to their user profile on the CERN Profiles site. (ie. Silvia Tomanin)

This module allows you to manage permissions for content types by role and author. It allows you to specifiy custom view, edit and delete permissions for each content type. Optionally you can enable per content access settings, so you can customize the access for each content node.

In the CERN environment, this can be used where you want to restrict access to a set of documents within a site to a specific e-group such as tasks for a project team.

The workbench module also provides some functionality in this area but it is more for managing the lifecycle of a document rather than protecting a particular content type from access/editing.

Provides a field type that can reference arbitrary entities:

• A generic entity reference field
• Four widgets:
  • Two implemented on top of the List module (Select and Radios/Checkboxes),
  • Two autocomplete widgets (one with one text field per entry, one tag-style with comma-separated entries in the same text field)
• Two formatters:
  • A "Label" formatter, with optional link that displays the label of the referenced entity (the node title, the user name, etc.)
  • A "Rendered entity" formatter, that renders the references entity using a configurable view mode
• Integration with Views (for both forward and backward references)
• Integration with Entity Metadata (and as a consequence with Search API and the like)
• Integration with Devel generate

The feeds module imports or aggregates data as nodes, users, taxonomy terms or simple database records.

This can be useful for interfacing to external systems and building content based on this data. A variety of formats are supported.

The module provides a simple API for scheduling tasks once at a predetermined time or periodically at a fixed interval.

This can be used to automate execution of standard scripts that modify the content of a site.

Also see the Rules module which can provide some pre-built functionality in this area.

Fields in content types which support URLs.

Seems a low impact module and useful function to be considered for inclusion in the default set and to be enabled for new sites,

Performs a scan of the links of a Drupal site.

A report is produced showing any links which give page not found errors or are permanently redirected.

The module generally works well but does have some problems with https.

The migrate module provides a flexible framework for migrating content into Drupal from other sources (e.g., when converting a web site from another CMS to Drupal). Out-of-the-box, support for creating core Drupal objects such as nodes, users, and comments is included - it can easily be extended for migrating other kinds of content. Content is imported and rolled back using Drush commands.

The rules module allows site administrators to define conditionally executed actions based on occurring events (known as reactive or ECA rules).

This is a very powerful functionality for automating actions and is often used by other modules to implement state changes or perform actions such as sending mails.

Tokens are small bits of text that can be placed into larger documents via simple placeholders, like %site-name or [user]. The Token module provides a central API for modules to use these tokens, and expose their own token values.