Ticket #39 (assigned enhancement)

Opened 3 years ago

Last modified 9 months ago

0016828: 4 [Still] Geen still tonen wanneer asset is afgeschermd en je geen toegang hebt

Reported by: admin Owned by: Frans
Priority: major Milestone: MediaMosa X.X
Component: Core Version:
Keywords: Cc:
MoSCoW: Must Have Estimated time after impact analysis:
Related to project: none Tested:
Accepted: no Estimated Hours:

Description (last modified by admin) (diff)


0016828: 4 [Still] Geen still tonen wanneer asset is afgeschermd en je geen toegang hebt
http://mantis.kennisnet.nl/view.php?id=16828

Geen still tonen wanneer asset is afgeschermd en je geen toegang hebt

Change History

Changed 3 years ago by admin

(0027089)
SURFnet - Frans (manager)
2009-05-26 12:29

Eens. Dit heeft te maken met issue 16844 (Afscherming op asset nivo mogelijk maken) die ik heb toegevoegd.

In mijn optiek spreek je van asset afscherming wanneer je de asset metadata afschermd volgens dezelfde regels als bij mediafile afscherming.

Wanneer je dit doet zijn automatisch de still(s) ook afgeschermd en de mediafiles (zelfs wanneer je niet expliciet afschermingsregels op de mediafiles zet).
(0027082)
klop01 (manager)
2009-05-26 10:46

Afscherming hebben we tot nu toe alleen nog maar gerealiseerd op mediafile niveau. Het kan zijn dat het orgineel is afschermd, maar de preview niet. In dit geval zou de still toch wel opvraagbaar moeten zijn.

We kunnen afscherming op asset definieren als: een asset is afgeschermd als er geen enkele mediafile afspeelrechten geeft. (Dit is echter performance niet erg handig.)

Of we kunnen afscherming op asset gaan implementeren. De code is hier al op voorbereid. We zullen dan in ieder geval de asset afscherming verder moeten uitwerken (wat is dan precies afgeschermd?, en welke relatie heeft asset afscherming op mediafiles, enz).

Changed 3 years ago by admin

  • description modified (diff)

Changed 3 years ago by Frans

  • component set to Core
  • related_to set to none
  • milestone changed from MediaMosa 1.6 to MediaMosa 1.7

Changed 2 years ago by Frans

  • milestone changed from MediaMosa 1.7 to MediaMosa X.X

Niet meer nodig voor SURFmedia

Changed 2 years ago by Frans

  • moscow set to Must Have

Changed 17 months ago by Frans

  • milestone changed from MediaMosa X.X to MediaMosa 2.3

Changed 17 months ago by peter

  • milestone changed from MediaMosa 2.3 to MediaMosa 3.0

Frans, Assume you meant 3.0.

Changed 14 months ago by forgacs

  • owner set to forgacs
  • status changed from new to assigned

Changed 14 months ago by forgacs

I have checked this issue.

Hiding stills in a protected asset is not a big problem.
But I'm not sure, we want to go this. Because then the stills won't be visible - this is good -, but all the data (eg. asset information, metadata) will be visible.

I have created a little summary about the current situation and a plan to discuss, what we may want:

Protection
==========

Current situation
=================

I. Protection type:
* Mediafile play protection

-----------------------------------------------------------------------
         \ GET call    |           |           |           | Asset
ACL type  \            | Asset     | Mediafile | Still     | Metadata
-----------------------------------------------------------------------
Mediafile is protected | No        | Play is   | No        | No
                       |           | protected |           |
-----------------------------------------------------------------------

II. Protection type:
* Mediafile share

-----------------------------------------------------------------------
         \ GET call    |           |           |           |
M/s type  \            | Asset     | Mediafile | Still     | Metadata
-----------------------------------------------------------------------
Mediafile is shared    | Shared    | Shared    | All #     | Shared
-----------------------------------------------------------------------

# All stills under that mediafile

Proposed plan
=============

All the new proposed protection types are compatible with the old ones.

I. Protection type:
* Mediafile play protection

-----------------------------------------------------------------------
         \ GET call    |           |           |           | Asset
ACL type  \            | Asset     | Mediafile | Still     | Metadata
-----------------------------------------------------------------------
Mediafile is protected | No        | Play is   | No        | No
                       |           | protected |           |
-----------------------------------------------------------------------

* View protection

-----------------------------------------------------------------------
         \ GET call    |           |           |           | Asset
ACL type  \            | Asset     | Mediafile | Still     | Metadata
-----------------------------------------------------------------------
Asset is protected     | Protected | Protected | Protected | Protected
-----------------------------------------------------------------------
Mediafile is protected | No        | Protected | Protected | No
-----------------------------------------------------------------------

II. Protection type:
* Mediafile share

-----------------------------------------------------------------------
         \ GET call    |           |           |           | Asset
M/s type  \            | Asset     | Mediafile | Still     | Metadata
-----------------------------------------------------------------------
Mediafile is shared    | Shared    | Shared    | All #     | Shared
-----------------------------------------------------------------------

# All stills under that mediafile

What is your opinion?

Changed 14 months ago by Michiel.Schok

Peter, what is the definition of 'shared'?
Is it the absence of domain, group en realm-ACLs?
Or is it the presence of an aut_app ACL?

In the distant past, we always had a mantra:
"Metadata is public, the content is not".
Title, description etc. was obvious metadata, video and audio was obvious content.
But for stills the distinction was not so clear. Some view a still as metadata, others as content.

For SURFmedia we made the choice of stills as content. We don't show stills (but instead show a lock-symbol) in our search results when a viewer doesn't have viewing rights on the video.

Changed 13 months ago by forgacs

  • owner changed from forgacs to arjen

Changed 11 months ago by Frans

  • owner changed from arjen to forgacs

Changed 10 months ago by forgacs

This ticket is involved in ticket #32 (0016844: [Core] Afscherming op asset nivo mogelijk maken) and the discussion about the development or possible solutions continue there.

Changed 10 months ago by forgacs

  • owner changed from forgacs to Frans

Changed 9 months ago by Frans

  • milestone changed from MediaMosa 3.0 to MediaMosa X.X

This issue is related to #32 and will be moved to MediaMosa X.X as well.

Note: See TracTickets for help on using tickets.