fcode/delarte
3
2
Fork 1
Code Issues 1 Pull requests 1 Projects 1 Releases Activity

Support for collections #7

New issue
Closed
opened 2022-12-10 08:32:07 +01:00 by Barbagus · 6 comments
Barbagus commented 2022-12-10 08:32:07 +01:00
Collaborator
Copy link

Some programs are organized in playlists. For instance a documentary split into few episodes.

For example: https://www.arte.tv/fr/videos/RC-020741/corpus-christi/

We propose to handle such playlist by allowing to download all episodes sequentially.

Some programs are organized in playlists. For instance a documentary split into few episodes. For example: https://www.arte.tv/fr/videos/RC-020741/corpus-christi/ We propose to handle such playlist by allowing to download all episodes sequentially.
Barbagus added reference stable 2022-12-10 08:36:59 +01:00
Barbagus commented 2022-12-10 14:06:56 +01:00
Author
Collaborator
Copy link

If we query the config API with the playlist identifier (RC-020741), the ConfigPlayer object returned is the one of the first "episode" of the list.
The program identifier (in .data.attributes.metadata.providerId) in then different than our playlist identifier.

This is our clue to understand that the program page URL is in fact a playlist page URL.

There is a playlist API entry point, in our example:

https://api.arte.tv/api/player/v2/playlist/fr/RC-020741

The response contains reference to every episode of the list in order... So there is a way.

If we query the _config API_ with the _playlist identifier_ (`RC-020741`), the `ConfigPlayer` object returned is the one of the first "episode" of the list. The _program identifier_ (in `.data.attributes.metadata.providerId`) in then different than our _playlist identifier_. This is our clue to understand that the program page URL is in fact a playlist page URL. There is a _playlist API_ entry point, in our example: `https://api.arte.tv/api/player/v2/playlist/fr/RC-020741` The response contains reference to every episode of the list in order... So there is a way.
Barbagus commented 2022-12-10 16:40:26 +01:00
Author
Collaborator
Copy link

The response contains reference to every episode of the list in order

well, not always it seems.

https://api.arte.tv/api/player/v2/playlist/fr/RC-021792

...has an empty data.attributes.metadata.items

> The response contains reference to every episode of the list in order well, not always it seems. `https://api.arte.tv/api/player/v2/playlist/fr/RC-021792` ...has an empty `data.attributes.metadata.items`
freezed removed reference stable 2022-12-11 23:04:42 +01:00
freezed added this to the devel project 2022-12-11 23:07:03 +01:00
freezed commented 2022-12-12 00:04:18 +01:00
Owner
Copy link

If needed, another topic related playlist stream:

(delarte) user@machine ~/tmp % delarte https://www.arte.tv/fr/videos/RC-023064/frankenstream 
Invalid program
zsh: exit 1     delarte https://www.arte.tv/fr/videos/RC-023064/frankenstream
If needed, another topic related playlist stream: ```bash (delarte) user@machine ~/tmp % delarte https://www.arte.tv/fr/videos/RC-023064/frankenstream Invalid program zsh: exit 1 delarte https://www.arte.tv/fr/videos/RC-023064/frankenstream ```
Barbagus commented 2022-12-12 08:35:46 +01:00
Author
Collaborator
Copy link

yep, that is because for now, one way to validate the ConfigPlayer object sent by the API is to veryfy it's .data.attributes.metadata.providerId is in fact the program identifier from the url (RC-023064 in your case) which is not the case for playlist urls.

It is indeed, I guess, one way to programatically figure out that the user intend to grab a whole playlist and not just one episode.

yep, that is because for now, one way to validate the `ConfigPlayer` object sent by the API is to veryfy it's `.data.attributes.metadata.providerId` is in fact the _program identifier_ from the url (`RC-023064` in your case) which is not the case for playlist urls. It is indeed, I guess, one way to programatically figure out that the user intend to grab a whole playlist and not just one _episode_.
Barbagus commented 2022-12-12 08:44:10 +01:00
Author
Collaborator
Copy link

The response contains reference to every episode of the list in order

well, not always it seems.

https://api.arte.tv/api/player/v2/playlist/fr/RC-021792

...has an empty data.attributes.metadata.items

It seems there is some sort of linking between episodes that can be followed using a playlist API call with and episode identifier.

> > The response contains reference to every episode of the list in order > > well, not always it seems. > > `https://api.arte.tv/api/player/v2/playlist/fr/RC-021792` > > ...has an empty `data.attributes.metadata.items` It seems there is some sort of linking between episodes that can be followed using a `playlist` API call with and _episode identifier_.
Barbagus referenced this issue from a commit 2023-01-09 19:48:46 +01:00
Refactor models and API
Barbagus commented 2023-01-09 20:31:32 +01:00
Author
Collaborator
Copy link

The response contains reference to every episode of the list in order

well, not always it seems.

https://api.arte.tv/api/player/v2/playlist/fr/RC-021792

...has an empty data.attributes.metadata.items

It seems there is some sort of linking between episodes that can be followed using a playlist API call with and episode identifier.

So far:

  • the items of the Playlist API object is not reliable,
  • the linking is rather terrible and requires two API calls (ConfigPlayer and Playlist) for each item.

An other aproach could be to actually load the HTML page and do some digging. From the look of it the site uses nextjs and include some JSON data that is used to build the HTML page. In that JSON we have everything we ask for (I checked).

The downsideis: relying on HTML implementation is likely less robust than just using their JSON-API, to say it otherwise: a change in thei WEB infra would kill our script.

I am torned.

> > > The response contains reference to every episode of the list in order > > > > well, not always it seems. > > > > `https://api.arte.tv/api/player/v2/playlist/fr/RC-021792` > > > > ...has an empty `data.attributes.metadata.items` > > It seems there is some sort of linking between episodes that can be followed using a `playlist` API call with and _episode identifier_. > So far: - the `items` of the `Playlist` API object is not reliable, - the linking is rather terrible and requires two API calls (`ConfigPlayer` and `Playlist`) for each item. An other aproach could be to actually load the HTML page and do some digging. From the look of it the site uses [nextjs](https://nextjs.org/) and include some JSON data that is used to build the HTML page. In that JSON we have everything we ask for (I checked). The downsideis: relying on HTML implementation is likely less robust than just using their JSON-API, to say it otherwise: a change in thei WEB infra would kill our script. I am torned.
Barbagus changed title from Support for playlists to Support for collections 2023-01-11 18:31:36 +01:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
stable
model
devel
draft
No results found.
Labels
Clear labels   
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
wontfix
This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
devel
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fcode/delarte#7
No description provided.