import

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.

Thanks.

As a student representing my college, I am organizing an online quiz on open source for a group of five colleges on 18 April 2009 which has more than 100 questions. I was lazy to upload question manually one by one so i wrote a quiz_questions_import script based on this article http://acquia.com/blog/migrating-drupal-way-part-i-creating-node. Bulk question import is a something often often asked feature in quiz issue queue so like to share this script with you guys here.

quiz_questions_import.php


<?php
require 'includes/bootstrap.inc';

moved to a wiki http://groups.drupal.org/node/21338

Overview: Transformations is an API for creating and executing data transformation pipelines, enabling higher-level modules to build stuff like Yahoo! Pipes or targeted import/export interfaces on top of it. The purpose of this project is to improve and build upon Transformations so that it not only provides a base framework but also satisfies a larger number of end-user needs, for example an AJAXified user interface.

Description:

Transformations was born out of the desire for a solution that can map any kind of structured data to any kind of other data, such as importing CSV or more complex XML files into Drupal nodes (with field mappings, obviously), exporting the data to the same files, or, if you will, providing an online converter that converts any RSS feed into Atom for example.

When performing such a large-scale transformation, some elements of the source data will likely need to be transformed on a smaller-scale level, e.g. you might need to convert a Unix timestamp into ISO date format at some point, or remove commas from a number string ("1,099.90") to conform to the target format, or perform string replacements on a given string field. At times, you might even need a combination of those transformations, or reference some other entity to construct the desired output data.

In order to do that kind of stuff, a simple mapping screen is not flexible enough, or would require lots of custom code to handle the more specific tasks. Transformations tries to solve that problem by splitting individual data transformation tasks into individual "operations" that can be chained into a larger transformation pipeline.

Based on the discussions we had at DrupalCon, I've written up the beginnings of an API with a standardized set of hooks and some functions.

The details of how, for instance, the block module would save an object to disc might start through using the not-so-desirable form API, due to lack of another option. In the future, however, this could be changed using a more optimal method.

Also included is a generalized function to fetch set of default objects that are embedded in PHP (like views module or context module implement).

Discussion is encouraged. :-)

io.module

The install profile API became the most important helper for building Drupal profiles. It provides a library of create functions that supports the most important Drupal modules and provisions a place for contributing more create functions.

Problems:

• In the Drupal 5 version, install profile API contains a wizard that generates install profile stubs and defines export functions for some of the API's install functionality, in Drupal 6 there is no successor for install profile wizard yet.

I'm excited about building a module that, if designed properly, would useful to others. I see how it might be useful for the development of a human resources department for personnel reviews and really any place where reports or static documents pass from one party to another.

I am building a community site based around an organization. We produce custom reports for many of the community members and provide them through a very simple and custom php app on our website. I want to move this to drupal to take advantage of the other powers to build community, as well as flexibility to improve access to these reports for archive purposes.

This has been floating around in my head for several months, but I've not developed a drupal module before so I crave review, comment and even participation.

As I have worked with different content management and middleware solutions, one problem I have encountered numerous times, and that I think needs a better solution in drupal, is import and export of data and provision of web services. I think it would be good for drupal to create an import/export framework that would allow drupal developers to make re-usable, sharable import and export modules by implementing PHP objects to a few commmon interfaces and then adding their new import/export type into a central, common import/export module.

This is especially relevant for modern corporate newspapers that need to integrate content from different legacy systems, produce that content, then send it off to a number of different web publishing systems, and then also face the prospect of their systems changing if they are bought or sold. The framework as outlined in the design below could also be a means of implementing REST services (SOAP or XML-RPC would probably require another layer on top of this, though you probably could do it in this framework).

i'm working on a replacement site using Drupal and phpBB3. I already have a phpBB3 forum up and running, and have around 27500 posts and over 1300 users.

I've managed to install the phpBB module, and get users to be able to log in, and post, play around etc.

I know this isnt production ready yet, and i'm just playing around, but how would I go about inserting all my existing data into this bridge? db backup and then upload it?

Hi.. I'm currently investigating http://drupal.org/project/docbook because i'd like to port that to drupal 5.x
But in the meantime i also found out about this http://drupal.org/project/importexportapi module, so i was thinking of rewriting the original docbook module and let it depend on this import API. No need to reinvent the wheel, and i guess that by doing so i only need to bother with the docbook format and no longer with the whole XML parsing.
I'm a right? Is there anyone interested in collaborating with me?

Greetz.