import

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.

I've been musing about the possibility of building a module for mass importing contents from existing sites, as an aid for migration to Drupal. I came across a potential model, an import utility for the CMS SAPID, http://sapid.sourceforge.net/en/doc/import/, code at http://prdownloads.sourceforge.net/sapid/migrator.tar.gz?download. The approach combines web crawling with regular expression-based data extraction. Users input the wrapping code patterns to search for, e.g., main content might be wrapped in and or maybe a div with a given class name.

[Some questions/suggestions that are kinda late in the game, but coming from research I've been doing today....]

To what extent is this API intended to facilitate data exchanges between Drupal and other CMSs?

Have you seen the Portable Site Information PSI specification, http://psilib.sourceforge.net/? It sets out a generalized XML interchange format for CMS data (and provides some tools written in Python). Would it be useful to consider this as a basis for the Import/Export XML format?

A potentially useful reference is the Exorcist softare produced as an offshoot of the Midgard CMS, http://www.midgard-project.org/documentation/exorcist/. It provides a general toolset for data exchanges between CMSs (in Java).

We are working on several online shops using Drupal + the e-commerce package. At the moment we are looking into integration with backend systems and datafeeds. Using either Drupal modules or programs which will interact directly with the drupal/e-commerce database.