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

FITS is god-awfully slow. Let's replace it. #18

Closed
mjgiarlo opened this issue Mar 4, 2014 · 12 comments
Closed

FITS is god-awfully slow. Let's replace it. #18

mjgiarlo opened this issue Mar 4, 2014 · 12 comments

Comments

@mjgiarlo
Copy link
Member

mjgiarlo commented Mar 4, 2014

And it's also not great for A/V files. Since we've already got hydra-file_characterization, which wraps characterization tools, and the only benefit of using FITS is that it wraps characterization tools, I vote in favor of leaving FITS behind. Another downside of FITS is that the released versions often wrap outdated versions of the tools. Instead of FITS, we could directly wrap JHOVE(2), Exiftool, MediaInfo, file, DROID, and possibly others (FIDO?).

@dchandekstark
Copy link
Member

👍

@jcoyne
Copy link
Member

jcoyne commented Mar 4, 2014

I believe that @mjgiarlo picked FITS for Scholarsphere (which became sufia, which spun off hydra-file_characterization), so I believe he is highly qualified to make this decision.

👍

Is Penn State going to lead this effort?

@mjgiarlo
Copy link
Member Author

mjgiarlo commented Mar 4, 2014

I'm also at a meeting where I've learned about some of the inefficiencies of FITS, hence where this came from.

If I were writing code, we'd lead this effort -- our other devs are maxed out on our ScholarSphere 2.0 effort. Maybe it's something I could hack on at LDCX, though?

@dchandekstark
Copy link
Member

+1 on LDCX hacking

@ruebot
Copy link

ruebot commented Mar 4, 2014

subscribes

@mjgiarlo
Copy link
Member Author

Brief update: this was not on the docket for LDCX, but now that we have @awead on staff, who is keenly interested in this work, things may get moving soon!

@ruebot
Copy link

ruebot commented Apr 25, 2014

Since y'all use Solr and we use Solr in Islandora, the Tika integration is pretty great. But iirc, that comes from the GSearch side of things that y'all don't use. My outsider 2¢.

@mjgiarlo
Copy link
Member Author

We do in fact have Tika in our Solr install, and though Tika wasn't listed above, it is on our Redmine ticket for this (an older ticket that pre-dates Sufia and our usage of GitHub issues). Thanks for adding that into the mix, @ruebot!

@mjgiarlo
Copy link
Member Author

We may attach this work to an upcoming sprint with @jcoyne (et al.) this spring/summer. Stay tuned, and pls keep the great ideas coming!

@ruebot
Copy link

ruebot commented Apr 25, 2014

Glad to hear!

@ruebot
Copy link

ruebot commented Apr 25, 2014

Just remembered... y'all know about FITS with Nailgun? Might be worth bench marking with other characterization tools.

@mjgiarlo
Copy link
Member Author

Yeah, thanks for adding that to the discussion. I believe @mistydemeo may have done some benchmarking there and it seemed like she was still leaning towards ditching FITS for Archivematica.

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

4 participants