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

Autogenerate images in the media center #69

Open
barbayellow opened this issue Jan 31, 2017 · 9 comments
Open

Autogenerate images in the media center #69

barbayellow opened this issue Jan 31, 2017 · 9 comments

Comments

@barbayellow
Copy link
Contributor

We need to give love to our mediacenter. Very often we forget to add thumbnails for the media in the mediacenter and it is sad. If there no thumbnails we should find a way to add those automatically. There s a script for that : https://wiki.bsf-intranet.org/doku.php?id=ideascube:importmedia#preview

@fheslouin
Copy link
Collaborator

I think we said that the thumbnails will be generated with the package build with csv2pkg.
For media mass import we did not choose to generate thumbnails as the set of software to do it was pretty huge...

Do we agree ?

@bochecha
Copy link
Contributor

For media mass import we did not choose to generate thumbnails as the set of software to do it was pretty huge...

Do we agree ?

This is what I remember as well.

And it's not that we need to install lots of stuff on the servers, it's also that LibreOffice (to generate PDF thumbnails) might be "slightly" too demanding for the Koombooks. 😄

I think we said that the thumbnails will be generated with the package build with csv2pkg.

This one I don't remember.

It's certainly possible, however two things to keep in mind:

  • the big amount of software to install is still required in this case, just not on the boxes but instead where csv-to-pkg gets run.
  • automatically thumbnailing some media could result in poor thumbnails (e.g for movies, which frame to you keep as a thumbnail? the first one? a random one?)

But those are details. I certainly love the result produced by totem-video-thumbnailer.

@fheslouin
Copy link
Collaborator

fheslouin commented Mar 14, 2017

This one I don't remember.

I was not clear enough, currently we do this job by hand on a server with all the set of software installed.

will be generated with the package build with csv2pkg.

I was meaning we do it in the same time of generating the package. If csv2pkg was able to do that as well that would be even better :)

@barbayellow
Copy link
Contributor Author

I think we said that the thumbnails will be generated with the package build with csv2pkg.
Don't remember either. However I remember we said the thumbnail will always be in the packages. Generated by BSF on BSF server where we can install anything we want.

I am really not sure it should be csv2pkg purpose to generate thumbnails since as its name states, csv2pkg is only here to create packages from csv files. Not to generate thumbnails.

@mgautierfr
Copy link
Member

Shouldn't be to the omeka plugin (or omeka itself) to generate the thumbnail ?
It would allow better handling of the thumbnail (changing it if it is not good enough, ...)

@letompouce
Copy link
Member

When it comes to BSF mass imports, thumbnails are now generated right from the Omeka server (not omeka itself - yet).

Still, a thumbnail should be generated when one uploads some media to the mediacenter.

@fheslouin
Copy link
Collaborator

Yes that would be nice. The only drawback is the pile of software needed to generate a thumbnail...

@swbsf
Copy link
Collaborator

swbsf commented Aug 25, 2017

Actually I've moved from the totem and evince thumbnailers to other tools with much less dependencies. ffmpegthumbnailer and convert. Still quite a few dependencies, but much less ;)

@bochecha
Copy link
Contributor

One problem with ffmpeg: patents make it hard to distribute in many parts of the world.

It's something to keep in mind.

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

No branches or pull requests

6 participants