You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per WordPress/openverse-catalog#311, integrating audio into CC Catalog will require a few different things. This issue hopes to keep track of everything relevant to the development of AudioStore.
(NEW) means a field that was not in ImageStore that was added to AudioStore
Current schema (in audio.py):
Foreign ID
Landing URL
Audio URL
File format (NEW)
Thumbnail URL
Filesize
Duration (NEW)
Samplerate (NEW)
Bitdepth (NEW)
Channels (NEW)
License (like ImageStore, license and license version)
Creator
Creator URL
Title
Collection/Album (NEW)
Type (music, podcast, lecture) (NEW)
Genre (NEW)
Language (NEW)
Metadata
Tags
Provider
Source
Other data to keep, but inside metadata rather than dedicated columns:
Date of publishing
Instruments
Mood
Description
Bitrate (as provided by source, rather than calculating ourselves from samplerate and bitdepth)
Views
Number of ratings
Numbers of comments
Related (list of foreign IDs of sounds which source considers to be similar)
Inappropriate columns for AudioStore that are in ImageStore:
Width
Height
Watermarked
Original Comments:
Issue author mariuszskon commented on Fri Mar 13 2020:
I am uncertain about the "type" field (as in music, podcast, lecture) and if it could be combined with genre in some way, or if we should keep it separate. What do you think @mathemancer ? source
Issue author mariuszskon commented on Fri Mar 13 2020:
@mariuszskon I think Genre and Type are different. We could probably come up with a list of 'allowed' types, e.g., music, podcast, lecture. Then, within music, we'd have the genres: rock, pop, classical, jazz, etc. On the other hand, in the 'podcast' type, for genre, we'd have: 'science', 'comedy', 'news', etc. source
mathemancer commented on Mon Mar 16 2020:
@brenoferreira Do you have any guidance or ideas based on what you'd like to have available to the front end here? source
brenoferreira commented on Mon Mar 16 2020:
Based on some of the designs here, it seems very comprehensive to me.
The frontend probably won't look exactly like this, but it'll probably be inspired by it. The only thing missing from the metadata list here are things like music instruments and mood. But I think that's ok source
Issue author mariuszskon commented on Tue Mar 17 2020:
@mathemancer Indeed I see the distinction much more clearly, and it is certainly worth having them separate. source
Issue author mariuszskon commented on Tue Mar 17 2020:
@brenoferreira instruments and mood can be added no problem, but I am concerned that audio sources might not have this information available for ingestion. source
brenoferreira commented on Tue Mar 17 2020:
yes. that's what I meant. If the source has the info, great. But if not, it
should be fine for now
On Mon, Mar 16, 2020 at 11:33 PM Mariusz Skoneczko [email protected]
wrote:
This issue has been migrated from the CC Search Catalog repository
As per WordPress/openverse-catalog#311, integrating audio into CC Catalog will require a few different things. This issue hopes to keep track of everything relevant to the development of AudioStore.
(NEW) means a field that was not in ImageStore that was added to AudioStore
Current schema (in
audio.py
):Other data to keep, but inside metadata rather than dedicated columns:
Inappropriate columns for AudioStore that are in ImageStore:
Original Comments:
Issue author mariuszskon commented on Fri Mar 13 2020:
Issue author mariuszskon commented on Fri Mar 13 2020:
mathemancer commented on Mon Mar 16 2020:
mathemancer commented on Mon Mar 16 2020:
brenoferreira commented on Mon Mar 16 2020:
Issue author mariuszskon commented on Tue Mar 17 2020:
Issue author mariuszskon commented on Tue Mar 17 2020:
brenoferreira commented on Tue Mar 17 2020:
On Mon, Mar 16, 2020 at 11:33 PM Mariusz Skoneczko [email protected]
wrote:
--
Thank you
Breno Ferreira
Front-end Engineer
Creative Commons
source
The text was updated successfully, but these errors were encountered: