#327 Feature request: Merge importexportbib to the core

[Joachim]

Hi,

the "Plugins" menu to me seems not a good place for a central feature as Export bibliographies. Don't think the average user will look at "Plugins". Of course, the same goes for others like the upcoming Word plugin. Is it possible to move Ex-/Import to "Resources" (to me the most logical place).

Best
Joachim

[Mark Grimshaw]

Hi Joachim,

This was where it all was before. You might be right though so I will look into it. The Word add-in (and the google docs one that has just been finished as well as the LO one underdevelopment) are completely separate to the wikindx installation – they're installed in the word processors themselves.

Mark

[Stéphane Aulery]

In fact the export / import functionalities overlap with the resource menu and the plugin menu. It would be better to have them in one place. It is possible to put everything in the resource menu.

Personally, I dream of rewriting the export / import system with mappings and propose the export formats under a new type of components which only contains declarative code and no longer executable code in PHP.

But the main idea is a specialized component for export formats.

[Mark Grimshaw]

Yes, the overlap has been a minor bother. Export/import is already declarative/mapped (there's no other way) but perhaps there is a way to separate mapping and code (keeping the latter as core code and the former as installable components – maybe keeping one installed default as APA is kept for styles). After all, all mappings relate to one system only (the wikindx database structure for resources).

But this would be a big job – the style editor (which I intend to rework the interface for) would also need rewriting and what if wikindx users unbeknownst to us are using their own styles that will then no longer work? A conversion interface would need to be written.

There is also the possibility of using/importing and converting the style files used by zotero (I think).

I'll deal with import/export but a major overhaul of styles is something for the future.

Mark

[Stéphane Aulery]

After all, all mappings relate to one system only (the wikindx database structure for resources).

Users can define custom fields. Not a problem?

[Stéphane Aulery]

Yes, the overlap has been a minor bother. Export/import is already declarative/mapped (there's no other way) but perhaps there is a way to separate mapping and code (keeping the latter as core code and the former as installable components – maybe keeping one installed default as APA is kept for styles). After all, all mappings relate to one system only (the wikindx database structure for resources).

I don't understand why you talk about the style.

[Stéphane Aulery]

Instead of being a menu move it will become a merge of export / import functionalities in the core because this feature is central.

[Stéphane Aulery]

[Mark Grimshaw]

Ready for 6.4.8

Mark