Request for extra fields in API

[will-c]

I will post in this discussion all fields that seem to be missing as I
find them. To start with:

Sets:

- Release/catalogue number
- Release date

Tracks:

- Release/catalogue number
- Release date

[Hannes Tydén]

These fields will be added later this week.

> Sets:
>
>  - Release/catalogue number
>  - Release date
>
> Tracks:
>
>  - Release/catalogue number
>  - Release date

If anyone else has suggestions for additional information please post
them here.

Thanks

[will-c]

Also:

Sets
- UPC

Tracks
- ISRC

Would be useful

[er...@soundcloud.com]

good points, we're adding these two fields in the next few days to our
database and api.

[er...@soundcloud.com]

will,
now we're supporting UPC codes for sets and ISRC codes for tracks,
both in the GUI and through the API.
We've also made the fields you requested available through the API
(Release/catalogue number & Release date for both sets/tracks).

cheers // eric

On Sep 16, 6:10 pm, will-c <william.coa...@gmail.com> wrote:

[will-c]

I wonder if it would be a good idea if there was a way to add Artist
metadata to Tracks and/or Sets?

Even though the typical soundcloud user is usually himself an artist,
its not too uncommon that s/he has different pseudonyms for different
styles. And for user accounts which are organisations, would obviously
be of use.

[will-c]

User elements nested within other elements (Set/Track...) are missing
the id field. I can parse the URI field but maybe it would be nice if
didnt have too?

[Hannes Tydén]

The nested user elements are a thing we haven't really solved yet. The
problem is that the nested user is not complete, missing some of the
attributes and this must be signaled in some way. A missing id might
not be optimal, but is a strong signal. Also I would like to add that
the ideal way to identify and address the resoures are by their uri:s,
since they are universally unique and you would never have to do any
translating.

We're also reworking the track/set metadata and their relationship to
users, this will probably be implemented within the coming month.