on the website http://blog.jthink.net/2014/08/jaikoz-7-introduces-self-hosted-discogs.html you wrote:
In the next few months we intend to self-host MusicBrainz data as well,... I hope you add a switch to use the original MusicBrainz database to add new releases and to retrieve then the just assigned new data like MB-RecordingId, MB-ReleaseId a.s.o
What is your method?
I'm aware that some users like yourself use Jaikoz to submit new releases to MusicBrainz and then tag their songs from MusicBrainz so I will have to work something out to make this possible with the new system. With the current implementation the self-hosted database is recreated every month from the Musicbrainz db (including all ids) so everything you add to Musicbrainz gets into the Jthink database, but currently there could be a delay of a month before seeing the newest data.
I will work out something for Jaikoz but haven't done so yet but Im thinking of a button on Jaikoz that lets you enter the release id of the new release and then Jaikoz will contact my server to add it to retrieve it and add it to the server db.
SongKong will use the new database before Jaikoz and does not require this feature so I will look at implementation after the SongKong release.
With the new release you may wonder how you can tag your songs to releases that you have just submitted from Jaikoz but have not made it to the JThink database yet. The good news is you can simply use Match to One Release:Match to Specified Release and enter the Musicbrainz Id (or Url) of the new release. If Jaikoz cannot find the release in Jthink db it will then check the MusicBrainz database.