Opened 8 years ago

Closed 5 years ago

#17 closed enhancement (wontfix)

Media Item with multiple sound files

Reported by: olivier Owned by:
Priority: major Milestone: 0.5
Component: Models Version:
Keywords: Cc:


In the EthnomusDatabase, some items are actually grouping several items. This means that for a single record in the item table (old "phono" table) there will be several sound files.

Eventually, it shouldn't be the case: a given item should correspond to a single sound file. However, in the EthnomusDatabase, the transition will require much manual work and time: there is about a thousand of those records and the splitting requires human interaction.

So, if we wait for those items to be properly splitted in the original 4D database, before we actually migrate the data to Telemeta, we are likely to waste a lot of time.

The solution I propose it to allow to bind several sound files to a given media item, so that the 4D database can be imported as-is. It will then be possible to do the manual cleaning inside Telemeta.

Change History (3)

comment:1 Changed 6 years ago by yomguy

  • Milestone set to 0.5

comment:2 Changed 6 years ago by yomguy

  • Component changed from Miscellaneous to Models

comment:3 Changed 5 years ago by olivier

  • Resolution set to wontfix
  • Status changed from new to closed

This clearly won't be implemented. Each item corresponds to one sound file. Chances are great that many of the audio files will be successfully imported, but not all of them .

The tasks of importing the remaining audio files, and splitting aggregated items will need to be performed either manually or by specific one-shot scripts. Such scripts, which might perform database transforms and such, will need to be implemented for specific situations. As such, those scripts are not in the scope of Telemeta.

Note: See TracTickets for help on using tickets.