export

I have been attempting to make a local version of a client's site for development. I was able to export a .gzip using phpmyadmin, but when I import it locally and compare to the live version, a lot of the tables are missing or are quite a bit smaller than the live version. A .zip export was only 4k so I assumed it was no good. The uncompressed database is around 117mb. I exported and downloaded it, and set the file size parameters in php.ini so that I don't get a "this database is too big" error.

Hi all,

I guess this is as good of a place to ask a question (maybe this could be discussed in one of our meetings).

I'm starting on a project (say site A) in which I will be setting up organic groups that would act as a stand-alone "sites" with their own users and nodes ( calendar and news,...) However, at some time in the future each one of these groups "could" branch out to be a full site (say site B, C)...
(The model is to offer possible FREE starting solution, to grow into a full PAID site)

Site A:
- Group 1
- Group 2
- Group 3
- Group 4

Group 2 ==>> Site B
or

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.

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

Hello all

We are researching social networks and online communities here at the Tampere University of Technology in Finland. In addition to developing them, we need also to study the behavior of the users in these networks. I guess the best term is social network analysis.

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.

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).

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 mentioned when this group started that we had written a simple module called Tearsheet. Its purpose is to let editors search for content and export plain-text formatted for pasting into a front-end system.

The original module is 4.6 and relies on a custom module that is unreleasable. But I was talking to Tim from Maine this week and he's trying to do export using Views and having trouble.