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](https://beta.musicbrainz.org/series/b2b031ec-176e-45fd-8965-4691a9e79691)
---
I wouldn’t say anything missing. Maybe some documentation for this. Cause I am unsure on how to trigger the other details.
For URLs, I tried mimicking the key, value pairs from the Release seed, and it did work for the Recording seed.
---
A description of how to seed general relationships is at [https://bitbucket.org/metabrainz/musicbrainz-server/pull-requests/1393](https://bitbucket.org/metabrainz/musicbrainz-server/pull-requests/1393)
---
Thanks for the link! It’s really help.
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.
Why is this?
Here is a test link: [OC ReMix: 3-D Ultra Pinball: Creep Night “Welcome to Our Castle” as a recording entry](https://musicbrainz.org/recording/create?edit-recording.name=3-D+Ultra+Pinball%3A+Creep+Night+%22Welcome+to+Our+Castle%22+OC+ReMix&edit-recording.length=4%3A15&edit-recording.artist_credit.names.0.name=Chernabogue&edit-recording.artist_credit.names.0.artist.name=Chernabogue&edit-recording.artist_credit.names.0.artist.id=1&edit-recording.url.0.text=http%3A%2F%2Focremix.org%2Fremix%2FOCR03044&edit-recording.url.0.link_type_id=306&rels.0.target=b2b031ec-176e-45fd-8965-4691a9e79691&rels.0.type=ea6f0698-6782-30d6-b16d-293081b66774&rels.0.attributes.number=OCR03044&edit-recording.edit_note=Recording+scraped+from+OverClocked+ReMix+%28http%3A%2F%2Focremix.org%2Fremix%2FOCR03044%29+using+the+OC+ReMix+import+script)
---
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`.
---