I found this presentation today from the guys at Yale who transitioned to Drupal: http://dl.dropbox.com/u/5585354/Drupal_On_Demand_PICC10.pdf
This presentation is for a technical audience, as it is mostly a discussion of the architecture. Very good stuff.
Hi! I haven't seen anything mentioned here about helping folks who aren't up to speed with Git getting up to speed with Git (couldn't resist). So -
The biggies -
There's some good stuff on here, especially the Book. The Book starts at the beginning, and I can't tell you where it ends, because I just haven't had to get that far with it yet.Read more
The Internet Corporation for Assigned Names and Numbers (ICANN) has an exciting new opportunity for an experienced Drupal developer to grow and maintain its family of Drupal websites. ICANN publishes a wide variety of content from a shared Drupal environment across several sites. Come join a team of experienced professionals in a pleasant, educational and challenging environment! Work will be performed primarily on-site in Marina Del Rey, CA, with periodic flexibility for telecommuting. Position reports to the Manager, Web Content Development.Read more
I'm working on a fairly large migration project. For this project, I will be migrating legacy data into Drupal 6. For this, I would like to create a new node with a specified nid so I can import data and maintain correct paths. I have looked everywhere for any tips on how to accomplish this, however, it doesn't seem like a very common practice. I have considered adding aliases, but for my case, I really feel like if I can directly map legacy ids to drupal nids, it will really make my life easier down the road. Has anybody had success doing anything like this?
I recently developed a website for a film festival.
People registered their film with a webform. After that, every film had to be re-added as regular nodes to appear on the website.
I had no time at that particular time, but I thought about a module migrating webform results to nodes, like Migrate does with databases, mapping webform fields to node & cck fields.
I've found nothing similar, does someone has ever seen a module doing that?
As we all know, one of Drupal's major shortcomings is exporting configuration. I believe that the source of this problem is that there is no standard way to store and retrieve settings. Most modules use variable_get and variable_set. The problem with this is that there is no association between a variable and a module.
I propose an api for saving and retrieving settings. I am currently working on a settings module as a proof of concept.
Here is a glimpse of the current api:Read more
I'm in the middle of implementing Update migrated content in-place, while thinking ahead to Workflow integration. The checkboxes on the current dashboard basically are defining a default workflow, for use by cron processing or the drush migrate all command, and adding the update option is making this just a little too complicated. So, I'm going to take a little poll here, followed by a description of what I'm thinking of in terms of a V1 dashboard and workflow approach, while anticipating a full implementation of defined workflows in a future version.Read more
New Handbook page: How to preserve old URLs during Drupal to Drupal migration by preserving nids and using mod_rewrite
Here it is: http://drupal.org/node/570906
Let me know if there are any grievous errors.
Digital Services Specialist, Boulder Public Library, Boulder Public Library - Main Branch
This is a 2 year temporary position.
40 hours per week
Apply by May 07, 2009
Salary Range: $21.88 - $26.25/hr
Required Education: Bachelor's Degree
Preferred Education: Master's Degree
Masters Degree in a program of Library and Information Studies preferred
Applications are required and must be received by 12 noon at 1101 Arapahoe on the closing date of the recruitment period. No exceptions.
An application is required for all city of Boulder jobs.Read more
The Data Import/Export and Migration to Drupal groups are being merged together. Data Import/Export was devoted to one project in this area while Migrate to Drupal was started for more general discussion - what we're going to do is close the group now known as Migration to Drupal and alter the charter for Data Import/Export to be more general (this is the easiest way to handle it, since Data Import/Export has the larger membership).
If you are a member of Migration to Drupal, you should join Data Import/Export to stay involved.