Comments

I wasn't aware of the exportables module until, just, after creating this one (thanks Robert Douglass).

I'm reviewing the exportables module, from what I have seen I like its approach. I'm in favour of joining forces, it looks like the exportables project is in its infancy and could use some contributors.

Status:Active» Closed (won't fix)

The current trend seems to be towards CTools: Exportables API. In an effort to consolidate and avoid fragmentation, I think I'm going that route.

Status:Closed (won't fix)» Active

Reopening to reflect http://drupal.org/node/521630 and http://drupal.org/node/789556 - two Features issues detailing the inclusion of vocabulary support. Note, however, that terms import/export is left to be supported by other modules.

Given these very recent developments, should development of this branch head in this direction to avoid duplication? If so, I may be able to devote some resources to this.

Hi c.ex! Great to hear the interest in a taxonomy_export / features integration!

I'm extremely busy at the moment, but am happy to open taxonomy_export CVS to a few contributors who are interested in cleaning up the 2.x branch.

Anyone interested?

Also extremely busy, but extremely interested in progress in this arena and may be able to devote time to it in the future, so "subscribe", if you will - and I'll re-visit when time/client needs permit. =)

Great to see the support! After I've wrapped up my latest project, I'll see if I can't devote some cycles to this myself.

Title:Duplicate ModuleTaxonomy export features / exportables integration

Changing title to reflect new direction of the discussion.

So, just to float some ideas around until I (or some other brave soul) can sit down to write a preliminary patch for this. Am I right in assuming that we'll need some way to manage machine names for terms, much in the same way Features is managing machine names for vocabularies?

Title:Taxonomy export features / exportables integrationTaxonomy export features integration

Changed the title to eliminate any ambiguity (the CTools API, which is used by features, versus the module).

regarding machine names, in the 2.x branch I have a bunch of logic for generating and maintaining machine names for vocabularies, but not individual terms.

Likely this code will need an overhaul as it was written quite a while ago. I'm guessing features + exportables has something to help solve this problem?

Surely CTools has something for that already in its API? I wouldn't know because I've never used it - thinking out loud here. Maybe this will help:
http://drupalcontrib.org/api/drupal/contributions--ctools--ctools.module/6

Version:6.x-1.0-beta1» 6.x-2.x-dev

Changing version to 2.x branch as that's where the Features integration is currently present.

Subscribing.

FYI, over in taxonomy_xml 2.0 I've been doing a lot with feature imports. (Exports, not so much)
Here is a sample, should (hopefully) work with taxonomy_xml 6.x-2.0
NZGLS (New Zealand Government Locator Services) Taxonomies

Taxonomy_xml is striving to be platform agnostic and its import and export formats avoid any Drupalisms - RDF taxa are the format of choice, though a half dozen alternatives are also consumed.

Taxonomy_xml is looking towards the source taxonomies being shared, remote resources, retrieved on-the-fly form URLs or web services - not distributed as files. I can do files (a dozen samples are included with the distro, and can also be distributed wih features now), but I'd rather do remote updates.
EG The MeSH (Medical Subject Headings) index I'm redistributing for (remote) re-import to your own site

... this therefore has a number of differences from this project, but maybe there is also some common ground

subscribe

Subscribe.

Subscribe.