You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.

Forum Discussion

ENGR_MANSOOR's avatar
ENGR_MANSOOR
New member | Level 2
3 years ago

I am working on coralNet API a web solution for coral reef Analysis.

I am working on the process of using the CoralNet API so that you can obtain sparse labels for an image using an already trained classifier (i.e. source). where we first submit a request to CoralNet using their API instructing which source we want to use, the image(s) we're trying to annotate, and the location we want the sparse labels to be (that's right, we get to specify). After submitting the request, we wait and periodically check back to see the progress. Once the request has been completed, we're sent back the annotations, which are then converted into a .csv file.

But Next we'll create a list of all of the images that are currently in the dropbox 'project_folder'. You can see below that we create a list called file_list and in it we store just a single image, which includes all of the metadata from dropbox. Note that you can increase the number of images you want to be annotated by the source by changing the num_images variable

 

But i get an error:

How to resolve this error please your cooperation will be highly appreciated

  • Greg-DB's avatar
    Greg-DB
    3 years ago

    ENGR_MANSOOR You'll need to enable the "files.metadata.read" scope on the "Permissions" tab of the app's page on the App Console, then click "Submit". Then, authorize the app again to get a new access token (and optional refresh token) as Здравко noted, since that change is not retroactive to existing authorizations.

  • Здравко's avatar
    Здравко
    Legendary | Level 20

    Hi ENGR_MANSOOR,

    All you need to change is already pointed out in the error message posted. Have you done it? If not, just do it. 😉

    Take in mind that associated scopes are "cached" within your token used! You need to revoke current token and reauthorize your application (login) anew, so the change can take effect.

    Hope this helps.

    • ENGR_MANSOOR's avatar
      ENGR_MANSOOR
      New member | Level 2

      Thanks for your kind reply. Actually I am getting confused in app authorization permission.

      What should select in permission tab to resolve the issue.
      Best regard!

      • Greg-DB's avatar
        Greg-DB
        Icon for Dropbox Staff rankDropbox Staff

        ENGR_MANSOOR You'll need to enable the "files.metadata.read" scope on the "Permissions" tab of the app's page on the App Console, then click "Submit". Then, authorize the app again to get a new access token (and optional refresh token) as Здравко noted, since that change is not retroactive to existing authorizations.