As an Opencast developer, I would like to know if the admin-ui should use it's own Admin-UI series endpoint anymore.
As an Opencast user and developer, I need to know the pros and cons of using "admin-UI series/series.json" over the "admin-UI resoures/series.json".
In particular, what benefits does the "admin-UI series/series.json" provide that justify it being much slower than the Admin-UI listprovider endpoint?
Also, does the Admin-UI even use it's own Admin-UI series endpoint enymore?
Does the Admin-UI listprovider series endpoint use SeriesService instead of just the Admin-UI index?
As you can configure list providers as data source for metadata fields only, having the extended list provider seems to be the way to go.
Thanks a lot for the SAXParser patch, btw. Quite cool how much improvement a single line change can provide!
@Sven Stauber Thank you for that explanation. I asked this question becaues our site created a custom series "extended title" listprovider (the exended title combines 3 series metadata, see attached). I was trying to figure out if that was Ok or if we should use be using the other endpoint.
The new patch to speed retrieval of SAXParser class resolves the issue for us for now.
IIRC, the series list provider only provides key-value pairs (series title & series ID) whereas /admin-ng/series/* provide all metadata ("benefit").
/admin-ng/series/series.json is used for the series table.
Another difference is that the list provider can be "bound" to metadata fields by configuration (see https://github.com/opencast/opencast/blob/develop/etc/org.opencastproject.ui.metadata.CatalogUIAdapterFactory-episode-common.cfg#L51).
In overall, I would tend to say that if only the pair [series title, series id] is required (usually the case for series selection), the list provider might by a good choice. For everything else, /admin-ng/series/* is required.