Collection

Collections are linked lists of files. The order of the lists is defined. This structure is appropriate for:

• galleries - collections of images
• playlists - collections of songs
• videos
• documents

Every user has collections that are generated by the server. They are useful for client-side purposes - the client stores his own statistics for these collections and then fills them with this files based on this data.

Please, do not modify or delete system collections.

The collections have the following structure:

Field	Description
id	int number of the collection
name	string name of the collection
created	datetime when the playlist was created
modified	datetime when the playlist was modified for last time
type	string what type of files could be kept in this list
ismine	bool is the playlist owned from the current user
system	bool if true, then the playlist was genereated by the server.
subtype	int If the collection was generated by the server, this indicates the exact collection type. Audio collections 1 - Recently Added 2 - Recently Listened 3 - Most Listened
contents	array list with the metadata of the files in the collection. These fileds are added: added datetime when the item was added to the playlist. position int the position of the item in the collection.

If the collection is shows its contens as pages, then these fields are added:

Field	Description
page	int the number of the current page. Starts from 1.
pagesize	int how many rows contains a single page. Default is 20.

Items from the collection are automatically unlinked, if the server cannot find these items.

This can occur, if the item was moved to trash or sharing of a folder was stopped.

The collection types are the following: For accessing the API methods:

Code	Description
0	generic collections - all type of files are allowed
1	playlists - only audio files are allowed in this collections

Returned in results:

Type	Description
generic	code=0
audio	code=1

---