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

Current WebVTT base file naming convention conflicts with Islandora Batch base file naming convention #1

Closed
bradspry opened this issue Mar 31, 2015 · 8 comments

Comments

@bradspry
Copy link

The currently required WebVTT file naming convention conflicts with Islandora Batch's base file naming convention.

Ideally, one would align the base file naming strategy with Islandora Batch, to enable command-line batch importing of oral histories.

OH123.xml
OH123.vtt
OH123.wav

@bradspry bradspry changed the title Current WebVTT file naming convention conflicts with Islandora Batch file naming convention Current WebVTT base file naming convention conflicts with Islandora Batch base file naming convention Mar 31, 2015
@bradspry
Copy link
Author

Attempting to batch import a zipfile with the following contents:
test.wav
test.xml
test_en.vtt

...results in a new object, with successful combination of test.wav and test.xml.

The presence of test_en.vtt however, causes the creation of a separate new object, with just test_en as the title of the MODS datastream.

If one renames test_en.vtt to test.vtt to align with the other files, islandora batch style, the transcript datastream is still not ingested during the batch process.

In summary, islandora_solution_pack_oralhistories is missing support for Islandora Batch import, but we are thankful for the developers who have brought the module to the very precipice of batch import support.

@Natkeeran
Copy link
Collaborator

Natkeeran commented Sep 26, 2016

Thank you reporting the issue.

I assume that test.xml is the MODS stream. OH module currently does not handle multiple vtts through batch! (I am currently reviewing the support for using multi-lingual VTTs). Thus, the batching is treating the test_en.vtt as a different object.

Also, Islandora Batch cannot handle xml data streams other than MODS or DC. There is an alternate approach suggested here: https://github.com/mjordan/islandora_solution_pack_xml/tree/7.x/modules/islandora_simple_xml_batch. However, we do to expect to support batch import in the short term.

@kstapelfeldt
Copy link
Contributor

not for this release: keep on Roadmap though.

@kstapelfeldt
Copy link
Contributor

kstapelfeldt commented Sep 20, 2017

To scope for next release - Islandora multi-importer may provide a workaround or use an approach similar to Mark's approach for supporting batch ingest in the XML solution pack. If so, we should document in the wiki documentation for those who wish to import batch oral histories.

@kstapelfeldt
Copy link
Contributor

@MarcusBarnes to do

@kstapelfeldt
Copy link
Contributor

Related to #72 and a general need to develop consensus around desired behaviour and what we wish to/can support, and how this is documented.

Minimum: Ability to batch ingest video/audio files and at least related XML transcript datastreams
Interface batch ingest zip loader is and will remain unsupported in the Islandora 7 version unless it's something easy to do.

Other issue: Are we providing a false affordance for people that suggests that interface ingest is possible? This needs to be reviewed with other content models that don't support batch. We could look at the XML solution pack and see what they are doing. We can also look at discimage and webarchive modules, which are part of the official release, and see if they are available under batch ingest.

@kstapelfeldt
Copy link
Contributor

@kimpham54 to test existing discimage and webarchive batch ingest via interface and report.

@MarcusBarnes
Copy link
Contributor

One can batch upload oral history objects using the Islandora Multi Importer. This will be documented as part of resolving issue #131.

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

5 participants