-
Notifications
You must be signed in to change notification settings - Fork 6
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
Comments
👍 |
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? |
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? |
+1 on LDCX hacking |
subscribes |
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! |
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¢. |
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! |
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! |
Glad to hear! |
Just remembered... y'all know about FITS with Nailgun? Might be worth bench marking with other characterization tools. |
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. |
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?).
The text was updated successfully, but these errors were encountered: