Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding two exports : multicolumn CSV output (for easy import to other tools) ; one list label for translation process #4

Open
gautiermichelin opened this issue May 1, 2016 · 7 comments

Comments

@gautiermichelin
Copy link
Contributor

Hi again,

I've hacked Tematres to add under the export menu two new options :

  • simple CSV export (code of the parent term, label of the parent term, code of the actual term, label, notes) intended to allow easy import for non ready skos tools
  • export with only one label per row for translation process

Are you ok for such a pull request ?
Do you want me to separate those ?

Bye,

Gautier

@tematres
Copy link
Owner

tematres commented May 3, 2016

Hi Gautier :), we work in the same direction, but in order to create a source file useful for any CSV ingest process, we see other tools who export structure like this:
term_id, term, type_relation/vinculation, term_id2,term2

and the same for notes or foreing relations. This model export more than one row for each term. Is less flat buy more simple. What do you think?

About export terms for translation process, in advaced options export form there are filtres to export only the terms without mapping relations, this option is useful for you? If you export terms with no options in Advanced reports you obtain CSV with one label per row. ok?

thank you!! :)

@gautiermichelin
Copy link
Contributor Author

Hi,

diego ferreyra mailto:[email protected]
3 mai 2016 13:41

Hi Gautier :), we work in the same direction, but in order to create a
source file useful for any CSV ingest process, we see other tools who
export structure like this:
term_id, term, type_relation/vinculation, term_id2,term2

and the same for notes or foreing relations. This model export more
than one row for each term. Is less flat buy more simple. What do you
think?

Not interested in this one for me, but this is definitely an alternative
for other tools. Why not implement both ? One CSV with one raw per term,
with parenthood, and other relations ; one CSV centered on the links.

About export terms for translation process, in advaced options export
form there are filtres to export only the terms without mapping
relations, this option is useful for you? If you export terms with no
options in Advanced reports you obtain CSV with one label per row. ok?

I'll have a check, thanks for the tip. Nevertheless, I've concat'ed the
code with the label (to avoid ambiguity on transifex returns to database
ingestion questions).

thank you!! :)


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#4 (comment)

Best regards,

Gautier

@tematres
Copy link
Owner

tematres commented May 6, 2016

Hi, Yes... may be the 2 options are useful :), we go ahead.

@marijane
Copy link

I just had a user ask if they can export our vocabulary to Excel, I could really use this. Is there a fork somewhere with this code?

@tematres
Copy link
Owner

hi @marijane , following the @gautiermichelin suggestion in the lasts version of tematres (3.0 and 3.1) we incude some reports oriented to export all the vocab to excel. In Reports you can found (all the terms, all the relations, all the notes) . It is the solution?

@marijane
Copy link

Aha! I was looking at the exports, not the reports.

These are interesting, but I suspect I need some kind of table-shaped export that shows the hierarchical relationships. I've asked my user what shape they need their data in, and I may try writing a SQL query to pull it.

@tematres
Copy link
Owner

Hi :) but if you can access to SQL environment, the best way is export SQL dump from Export menu (Menu -> Administration -> Export: SQL dump)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants