Ticket #63 (closed enhancement: fixed)

Opened 3 years ago

Last modified 2 years ago

0016765: 4 [Core] Aanpassing XML output opsomming mediafiles (Forum)

Reported by: admin Owned by:
Priority: major Milestone: MediaMosa 1.6
Component: Core Version: Tested and Accepted
Keywords: Cc:
MoSCoW: Estimated time after impact analysis:
Related to project: none Tested:
Accepted: yes Estimated Hours:

Description


0016765: 4 [Core] Aanpassing XML output opsomming mediafiles (Forum)
http://mantis.kennisnet.nl/view.php?id=16765

Zie: http://www.vpcore.nl/forum/viewtopic.php?f=5&t=18&start=0 []

Bij het opvragen van de details van een asset worden de gegevens van gekoppelde mediafiles teruggegeven.

De opsomming van mediafiles heeft de vorm :
<mediafiles>

<mediafile_1>
...
</mediafile_1>
<mediafile_2>
...
</mediafile_2>

</mediafiles>

Ik zou graag deze output veranderd zien naar de vorm:
<mediafiles>

<mediafile id="1">
...
</mediafile>
<mediafile id="2">
...
</mediafile>

</mediafile>

De huidige vorm maakt verwerking onnodig omslachtig en foutgevoelig naar mijn mening.
Voor de huidige "dynamische" element namen is geen XSD schema te maken. Een eenvoudige XPath query om alle 'mediafile' elementen op te halen is zo onmogelijk.
XML structureert documenten en maakt zo communicatie tussen applicaties mogelijk. De huidige manier is niet gestructureerd en bemoeilijkt die communicatie.

Change History

Changed 2 years ago by MC-arjen

  • status changed from new to closed
  • resolution set to fixed
  • accepted set to 0
  • component set to Core

fixed in 1.6

For backward compatibility we introduced versioning in the restcalls. In the admin interface, client applications, we introduced an field "Select active version:" where we can define the current version rest calls per ega. The latest version has the change mentioned above, including 1.6.0 and above.

It is possible to overrule this version in the rest call itself with the parameter "version" (see paragraph 2.2 of the webservice document).

/asset/J2k2qFEBnphMtAcNKsyGskTx?limit=10&version=1.5.0

gives the old format (mediafile_1 ..)

/asset/J2k2qFEBnphMtAcNKsyGskTx?limit=10&version=1.6.0
or
/asset/J2k2qFEBnphMtAcNKsyGskTx?limit=10&version=LATEST

/asset/J2k2qFEBnphMtAcNKsyGskTx?limit=10

gives the new format, unless the setting in the admin interface says otherwise.

Changed 2 years ago by MC-arjen

i meant:

/asset/J2k2qFEBnphMtAcNKsyGskTx?limit=10&version=1.6.0
or
/asset/J2k2qFEBnphMtAcNKsyGskTx?limit=10&version=LATEST

gives the new format.

/asset/J2k2qFEBnphMtAcNKsyGskTx?limit=10

gives the new format, unless the setting in the admin interface says otherwise.

Changed 2 years ago by Frans

  • accepted changed from no to yes
  • related_to set to none

Changes are approved. SURFmedia works in "latest" mode.

Changed 2 years ago by Frans

  • version set to Tested and Accepted
Note: See TracTickets for help on using tickets.