Alternatively, you might be able to download the musicbrainz DB and connect it to your access as well as the RD DB, use the user defined field to hold a linking key field to the MBID field in the music brainz db and generate a report from that query that includes what you need.
Again the MBID would have to be obtained from the musicbrainz db and input into the RD DB. Advantage here, is you can also use a copy of music brainz db that is linked and updated by their master db. On 08/08/2011 12:36 PM, VE4PER/Andy wrote: > If someone has access to a laptop with MSaccess on it, you could connect > to the > mysql RD data base and design a form for volunteer librarians to use to > input the extra data into the rd db instead of having to re-rip everything. > > That would look after all the legacy selections in the library; you' ll > need new ripping procedure to add new stuff. Until RD importer can add > all the detail from musicbrainz it might be an option to rip new CD's > using another ripper, like audacious or something like that, where you > can specify all the optional data you want from musicbrainz and also > what format so that it fits RD fields when you use rdimport to import > them all afterwards. > > Problem here is where do you add the extra data that RD doesn't yet > support; user defined field? or extra text at the end of the selection > name field so it doesn't show in the rdairplay window? > > Would be nice to just have the extra fields in the cart and cut tables > to accommodate it. > Although it is a simple matter to add the extra fields using access, it > may affect RD badly, and if re-installed on a new machine RD would > regenerate tables without those new fields. > > cheers > Andy > > > On 08/08/2011 03:46 AM, James Harrison wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> While it won't help you retroactively without some work to integrate >> it with the Rivendell database, and it's not a _perfect_ method, you >> should look at the MusicBrainz database. It's online, freely >> available, and contains ISRC and other data for most things. Not sure >> about UPCs or catalog numbers, but it will let you identify most >> albums (except where there's more than one album with the track on). >> >> I have MB support in IRIS (https://github.com/JamesHarrison/iris), a >> tool I put together a little while back to handle content ingest- I >> haven't had time to finish the Rivendell importer stage, though, so it >> can't yet directly insert things like ISRC data into the database >> (since rdimport won't accept that as an input, making a quick and >> dirty solution impossible). I think someone's experimented in the past >> with integrating the MusicBrainz Picard tagger with the Rivendell >> library- might be worth looking into that. >> >> Cheers, >> James Harrison >> >> >> On 07/08/2011 21:19, Bill Putney wrote: >>> We've used the RDLibrary ripper to rip CD's into our Rivendell. I >>> started looking at reports to send to the music licensing agencies. >>> It looks like most of the stuff they want is missing. I think there >>> are a few ISRC codes but it seems like most CDs don't encode them. >>> Most of the cuts have artist and title and that's it. There are no >>> album titles, record company marketing names, catalog numbers, UPC >>> codes and on and on. It sounds like if there is an ISRC code a lot >>> f the other info isn't required. >>> >>> Is there a way to retroactively get this info into our library or >>> do we have to start from scratch? >>> >>> Thanks, Bill Putney - KPTZ Port Townsend, WA >>> >>> _______________________________________________ Rivendell-dev >>> mailing list [email protected] >>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.9 (MingW32) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> >> iEYEARECAAYFAk4/XDEACgkQmJV2s0zjsDhqiwCZAWxSdvXdQee+xG6yv5fPa1T8 >> iCAAn1XJW6e/umiwMU+jRrSM8V9zTru4 >> =BrX9 >> -----END PGP SIGNATURE----- >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
