Ticket #11 (closed enhancement: fixed)

Opened 3 years ago

Last modified 2 years ago

0016880: Webservice for analyzing or re-analyzing mediafiles

Reported by: admin Owned by: marek
Priority: minor Milestone: MediaMosa 1.7
Component: REST Version: 1.7.0
Keywords: Cc:
MoSCoW: Estimated time after impact analysis:
Related to project: none Tested:
Accepted: yes Estimated Hours:

Description (last modified by admin) (diff)

At this moment it is only possible to analyze mediafiles using the Admin interface.
It would be nice however to have a REST call for that.


http://mantis.kennisnet.nl/view.php?id=16880

Op dit moment (1.5.6) is het alleen mogelijk om een mediafile te analyseren via de Media Management van de beheeromgeving.
Het zou fijn zijn om die functionaliteit ook in webservice - vorm te hebben.

[get] /{mediafile-id}/analyse

met als resultaat een job-id of errorcode

Change History

Changed 3 years ago by admin

  • description modified (diff)

Changed 3 years ago by Frans

  • priority changed from major to minor
  • component set to REST
  • milestone changed from MediaMosa X.X to MediaMosa 1.7

Changed 2 years ago by MC-arjen

  • owner set to marek
  • status changed from new to assigned
  • related_to set to none

documentation missing

Changed 2 years ago by robert

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

documentation was added by forgacs.

Changed 2 years ago by Frans

  • version set to 1.7.0

Changed 2 years ago by Michiel.Schok

Release notes:
#11 [get] mediafile/{mediafile-id}/analyse added to force a reanalyze.

Changed 2 years ago by Michiel.Schok

  • accepted changed from no to yes

Documentation on mediamosa/api:

[post] mediafile/{mediafile-id}/analyse &user_id={}

[post] would indeed be logical, and works as advertised.

It even works in 1.6.4 (as is documented on the mediamosa.org/api):

<?xml version="1.0"?>
<response>
  <header>
    <item_count>1</item_count>
    <request_process_time>0.0103</request_process_time>
    <request_query_count>16</request_query_count>
    <request_result>success</request_result>
    <request_result_description></request_result_description>
    <request_result_id>601</request_result_id>
    <request_uri>[POST] mediafile/Wb0gnYT3Zufyki9wIxc5aHyp/analyse</request_uri>
    <vpx_version>1.6.4</vpx_version>
  </header>
  <items>
    <item id="1">
      <job_id>502983</job_id>
    </item>
  </items>
</response>
Note: See TracTickets for help on using tickets.