Add audio/video metadata

[rperlin-ela]

Description

We'd like to import metadata automatically from Youtube and/or Archive.org and show it under the language name above the audio/video embed in the dialog. Probably the most important thing would be what both Youtube and Archive.org call the Description, but maybe a few other fields like rights, attribution. We also have this info in spreadsheet form if that’s easier.

Resolution

@abettermap thinks Youtube may have an API we can use

[abettermap]

@rperlin-ela

YouTube

We will definitely need an API key for this. Here are the steps, which are very similar to my instructions for setting up the Sheets API token except you can use the same project and even the API key, you just need to enable YouTube API:

1. https://console.developers.google.com/apis/dashboard

2. Select your project if needed:

   

3. If needed, click the project in the popup.

4. Click this:

   

5. Type youtube

6. Click the result with v3 in it:

   

7. Click ENABLE

Should be all set. Go back to your Dashboard and confirm it's there then let me know it's ready:

Archive.org

Question: why don't any of the records use this for audio yet? It looks like ELA has quite a few, just wondering why they're not in the dataset.

Anyhoo, no API key required. Here's an example of the meta for your "Kabardian comparative" for example:

https://archive.org/metadata/ela_kabardian_comparative/metadata

Which returns:

Or go straight for the kill with one level deeper: https://archive.org/metadata/ela_kabardian_comparative/metadata/description

That's the info we need, right? Easy on my end, BUT how will those files be embedded as audio? I see a bunch of formats listed, but also archive.org's docs suggest an iframe, which is normally used for videos.

The audio embed I have set up in the code is not going to do anything with an API URL like that, and vice versa. So, will I need to do a check to see if the Audio url includes archive.org then process it accordingly to make it work with one of these?

1. The webplayer/video thing to use as an iframe embed (I don't know enough about these formats)

2. Sift through the full API results for that file to find the WAVE?

   

I see how to get the full list as well, but I assume we'd only need one of them?

Here's a full list for another of your audio items as a comparison: https://archive.org/download/mid-2003-06-13c

I'm not sure we'll get away without me doing some kind of check/processing on my end, so I could see this being the flow of code:

1. You provide me with a consistent URL in Audio column to the wav file or whatever
2. I check Audio to see if it contains archive.org
3. If so, parse it out so I can get just the item ID (I don't like this already)
4. Use the ID to hit their API so that I can get the Description

OR, we treat it as a video/webplayer:

1. You populate the Video field with the embed URL, e.g. https://archive.org/embed/mid-2003-06-13c
2. I follow steps 3-4 above (3 is easier this way)

The obvious drawback of the "video" approach is that you couldn't have audio AND video for the same record.

OR:

1. you give me the metadata API URL and I sift through the results until I find the WAVE format (assuming it's always there).
2. I grab the Description while I'm there.

I'm going to be hitting the API no matter what so whatever is cleanest for that. Assuming there is enough consistency of results then I'm sure I could find whatever I need there and deliver it to the user in whatever format you want. Personally I would go with the "video" embed since it has a lot more options and could be useful for those languages that have like 100+ wave files:

If you've got instances of Video AND Audio though, then would be a harder sell for the embed approach. 🤔

For Future Jason

here is the archive's metadata API: https://blog.archive.org/2013/07/04/metadata-api/

[abettermap]

@rperlin-ela

Hope that made sense, kind just learning it as I go, so let me know what you think.

[rperlin-ela]

Great, thanks for these instructions. I’ll get on them once we’re ready to get started. Maybe this will be obvious once we’re working on it, but can we choose what metadata gets pulled by the API? Want to clarify this with Dan, whose request this was, but I think Description is the key thing, maybe one or two others. Re: Archive.org <http://archive.org/>, same deal— and yes, we have some things on there. (Aren’t we using the Neo-Mandaic sample from there?). But we're going to have a TON more— all of our audio— within the next year or so, we just wanted to wait until we have the best samples up there with all the proper metadata. Cool that a full list can be pulled, which is probably more than we need, but I’d want to ask Dan— potentially a neat capability. In principle all the code flows you describe sound sensible, but the ability to have both video and audio for any given language community would be nice.

…

On Oct 12, 2020, at 10:36 PM, Jason Lampel ***@***.***> wrote: @rperlin-ela <https://github.com/rperlin-ela> YouTube We will definitely need an API key for this. Here are the steps, which are very similar to my instructions <#18 (comment)> for setting up the Sheets API token except you can use the same project and even the API key, you just need to enable YouTube API: https://console.developers.google.com/apis/dashboard <https://console.developers.google.com/apis/dashboard> Select your project if needed: <https://user-images.githubusercontent.com/4974087/95803510-85ea2900-0cbd-11eb-8d90-599622bdb61f.png> If needed, click the project in the popup. Click this: <https://user-images.githubusercontent.com/4974087/95803555-a6b27e80-0cbd-11eb-9b4b-d3aef5b20cb1.png> Type youtube Click the result with v3 in it: <https://user-images.githubusercontent.com/4974087/95803375-2be96380-0cbd-11eb-8a6a-165009ca0d40.png> Click ENABLE Should be all set. Go back to your Dashboard and confirm it's there then let me know it's ready: <https://user-images.githubusercontent.com/4974087/95803467-6b17b480-0cbd-11eb-80ec-9f04a732a675.png> Archive.org Question: why don't any of the records use this for audio yet? It looks like ELA has quite a few, just wondering why they're not in the dataset. Anyhoo, no API key required. Here's an example of the meta for your "Kabardian comparative" for example: https://archive.org/metadata/ela_kabardian_comparative/metadata <https://archive.org/metadata/ela_kabardian_comparative/metadata> Which returns: <https://user-images.githubusercontent.com/4974087/95805410-94870f00-0cc2-11eb-8a33-1bc76b6c9440.png> Or go straight for the kill with one level deeper: https://archive.org/metadata/ela_kabardian_comparative/metadata/description <https://archive.org/metadata/ela_kabardian_comparative/metadata/description> That's the info we need, right? Easy on my end, BUT how will those files be embedded as audio? I see a bunch of formats listed, but also archive.org's docs suggest an iframe <https://archive.org/help/audio.php>, which is normally used for videos. The audio embed I have set up in the code is not going to do anything with an API URL like that, and vice versa. So, will I need to do a check to see if the Audio url includes archive.org then process it accordingly to make it work with one of these? The webplayer/video thing to use as an iframe embed (I don't know enough about these formats) Sift through the full API results <https://archive.org/metadata/ela_kabardian_comparative> for that file to find the WAVE? <https://user-images.githubusercontent.com/4974087/95806714-92727f80-0cc5-11eb-9da1-bf928f5cb8d0.png> I see how to get the full list <https://archive.org/download/ela_kabardian_comparative/clips%20Kabardian/> as well, but I assume we'd only need one of them? Here's a full list for another of your audio items as a comparison: https://archive.org/download/mid-2003-06-13c <https://archive.org/download/mid-2003-06-13c> I'm not sure we'll get away without me doing some kind of check/processing on my end, so I could see this being the flow of code: You provide me with a consistent URL in Audio column to the wav file or whatever I check Audio to see if it contains archive.org If so, parse it out so I can get just the item ID (I don't like this already) Use the ID to hit their API so that I can get the Description OR, we treat it as a video/webplayer: You populate the Video field with the embed URL, e.g. https://archive.org/embed/mid-2003-06-13c <https://archive.org/embed/mid-2003-06-13c> I follow steps 3-4 above (3 is easier this way) The obvious drawback of the "video" approach is that you couldn't have audio AND video for the same record. OR: you give me the metadata API URL and I sift through the results until I find the WAVE format (assuming it's always there). I grab the Description while I'm there. I'm going to be hitting the API no matter what so whatever is cleanest for that. Assuming there is enough consistency of results then I'm sure I could find whatever I need there and deliver it to the user in whatever format you want. Personally I would go with the "video" embed since it has a lot more options and could be useful for those languages that have like 100+ wave files: <https://user-images.githubusercontent.com/4974087/95808796-7b825c00-0cca-11eb-9088-7c44e3219755.png> If you've got instances of Video AND Audio though, then would be a harder sell for the embed approach. 🤔 For Future Jason here is the archive's metadata API: https://blog.archive.org/2013/07/04/metadata-api/ <https://blog.archive.org/2013/07/04/metadata-api/> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#72 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMNKB5F7OXGP5HIXUPBQJG3SKO4MLANCNFSM4QTE3FWQ>.

[abettermap]

Great, thanks for these instructions. I’ll get on them once we’re ready to get started.

Feel free to start any time, this might be one of the first things I work on since it's fresh in my brain.

Maybe this will be obvious once we’re working on it, but can we choose what metadata gets pulled by the API? Want to clarify this with Dan, whose request this was, but I think Description is the key thing, maybe one or two others.

If I'm understanding correctly, yes. Archive.org doesn't have more than what I showed in the screenshot I think, but as for YouTube there may be other metadata. You can skim through the options here: https://developers.google.com/youtube/v3/docs/videos#properties

Highlights from today's call

• Embeds are fine. Aka the Archive.org web player, aka <iframe>, aka Jason can remove the audio player component.
• Once the code is ready, Ross will point the Audio URL(s) to the embed URL format rather than the .wav. Example: https://archive.org/embed/ela_kabardian_comparative
• Jason will assume all audio is from achive.org

Transcript files

Unless these are part of something in the videos or audio files already in existence, I don't think this is an easy option. If you had an external file somewhere, like Dropbox, we'd have to either:

1. Add a new column like Transcript in the spreadsheet
2. Throw it at the end of Description
3. Use a CMS like Sanity

[abettermap]

@rperlin-ela should I assume that all the archive.org instances will have a playlist? Or maybe a better question is, is this format ok when they don't?

I don't think it's harming anything when there's only a single item, and it keeps the UI consistent with the instances which do have playlists.

[abettermap]

Re: additional metadata fields, I think you're also going to want title for both YouTube and Archive instances. Up until now I think I've been using the Endo, so title would be a nice upgrade.

[abettermap]

...and I think that's about all that's useful in the YouTube API. I know this just looks like code but you get the idea:

[rperlin-ela]

Yes, I think what's in there is now just Language, but Title followed by Description would be great.

I reckon some archive.org instances will have playlists but not all (as with Youtube). Format from the screenshot seems fine to me and good to keep consistent.

I believe the Youtube API is now enabled — let me know if not or if you need anything else from my end.

In case it helps I uploaded a new tileset just now with what I think should be the correct embed URL from Archive for Neo-Mandaic. (Sorry if that was jumping the gun—I see for the time being it's giving an error.)