Ticket #322 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

We don't see the Mediafiles when browsing the assets in the admin application

Reported by: Frans Owned by: robert
Priority: major Milestone: MediaMosa 2.2
Component: Core Version:
Keywords: Cc:
MoSCoW: none Estimated time after impact analysis:
Related to project: none Tested: yes
Accepted: yes Estimated Hours: 0

Description

We don't see any Mediafiles when browsing the assets in the admin application. Even if there are mediafiles.
ie.  http://beheer.vpcore.snkn.nl/admin/mediamosa/browse/asset/q1CRf9ZMdFAqXRHTewZi2nGo

Mediafiles (0)
This asset does not contain mediafiles.

Change History

Changed 3 years ago by Frans

  • moscow changed from Should Have to none

Changed 3 years ago by Frans

  • summary changed from We don't seen the Mediafiles when browsing the assets in the admin application to We don't see the Mediafiles when browsing the assets in the admin application

Changed 3 years ago by Michiel.Schok

On Core-acceptance there is another situation, possible related:
 http://beheer.acceptatie.vpcore.snkn.nl/admin/mediamosa/browse/asset/33535

There are three mediafiles on this asset, but 9 are shown. Maybe the three aut_app rules are involved?
Furthermore, the technical metadata on the 'same mediafile_id's is not identical: on two occasions the mime-type and some other attributes are missing, one is OK.

Changed 3 years ago by Frans

  • milestone changed from MediaMosa 2.1 to MediaMosa 2.2

Moved to MediaMosa 2.2
(we'll close the MM 2.1 release)

Changed 3 years ago by robert

  • status changed from new to closed
  • resolution set to fixed

Fixed -> 2.2 release.

In some cases the mediafiles where not shown, this is because we where browsing using all app_ids. In the used REST calls it only used the first app_id, which would have been (random) app_id most likely app_id 1.

This new layer in 2.0 where REST calls are run using the 'global' app user needs more testing. The REST calls for mediafiles under asset are now run using the app_id of the asset we are viewing. Same goes for collection.

The fix now shows the correct number of mediafiles under asset. However, its not exactly the same database as on acceptation.

Changed 3 years ago by MC-arjen

  • status changed from closed to reopened
  • resolution fixed deleted

Also, in some cases a number of mediafiles is duplicated. It seems there is a direct correlation to the amount of times a mediafile is master/slaved.

Changed 3 years ago by MC-arjen

  • owner set to robert
  • status changed from reopened to assigned

Changed 3 years ago by Michiel.Schok

The asset_id from the opening post contains 5 mediafiles when viewed on the POC-environment.
 http://core.mediamosa.surfnet.nl/admin/mediamosa/browse/asset/q1CRf9ZMdFAqXRHTewZi2nGo
(build 727)

Changed 3 years ago by Frans

  • status changed from assigned to closed
  • resolution set to fixed

Changed 3 years ago by Michiel.Schok

  • tested changed from no to yes
  • accepted changed from no to yes

Mediafiles are visible, counts are good, and master-slaved mediafiles only show up once.

Just one typo in the asset details page ( http://beheer.acceptatie.vpcore.snkn.nl/admin/mediamosa/browse/asset/33535).

Over there, there are 'autorisarion rules'. Me thinks that should be changed to 'authorization rules'.

Note: See TracTickets for help on using tickets.