I recently found the capabilities to Seed in releases, which some of the user-scripts tend to use when importing from other sources.
I have been looking over the functionality and want to tackle the seeding of recordings from OverClocked ReMix.
Upon initial investigation, the 'Add Recordings" has very basic support for injecting core recording data using the “edit-recording” attribute. By playing around with the GET directives, the following elements were are supported.
edit-recording
- name
- length
- artist_credit.names[x]
- irscs[x]
- comment
artist (with MBID)
Based on this, are there plans to extend the Seeding for recordings, how can the other elements be passes, and would it be possible to submit a User Script that can scrape the OC Remix recordings, and have relationships added to them, much like the recordings in the OC Remix Series? https://beta.musicbrainz.org/series/b2b031ec-176e-45fd-8965-4691a9e79691
I’ve designed a simple script that scrapes the data from the page and prepares it. I works well when sending a GET request by populating the field. Sending a POST request seems to create a full record. (Best to avoid that).
I need some clarification about one of the attributes. I have populated the record with Recording-Series relationship, and need to inject the ID of the track into the attribute, but it fails to be parsed.
Using “rels.x.butterfat.y.number” or “rels.x.attribute.number” both fail.
You aren’t following the format. Your example link contains this: rels.0.attributes.number=OCR03044 First, there may be multiple attributes on a relationship, so they need to be numbered. Second, the key for the attribute content isn’t number, but text_value. So rels.0.attributes.0.text_value=OCR03044 would be closer. However, you also need to specify the attribute type via ...0.type.
You can open an editor, choose your relationship and click the help button, that will show you its UUID.
You can see its numeric ID in the <select> code itself, IIRC, but anyway it’s the other one you need (the UUID).
Next, I tried prefixing those parameter names with edit-recording. since that seems to be needed for the non-artist parameters. (Why is artist different?)
I also tried rels.0.target and rels.0.type, rels.0.attributes.0.text_value and rels.0.attributes.0.type, and those pairs with edit-recording. prefixes.
In all of those cases, the “Relationships” and “External Links” sections remain empty, though.