Project

General

Profile

Actions

Question #1142

closed

API - issue with references and files

Added by Bernhard Koschiček-Krombholz almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
API
Target version:
-
Start date:
2020-02-12
Estimated time:

Description

The Api.get_file functions won't get result with reference entities.

Update:
I tested it with source + file and reference + file. Both show the file as the relation but only the source lists it as depictions. That's because with reference the file is linked in the opposite direction so the get_file functions doesn't "find" it.

Question to Stefan: is this
  • the correct behavior (link is valid and it's ok that the file isn't listed as depiction at the reference) Stefan says: YES
  • or is the link in the wrong direction (but as far as I remember it was on purpose)? Stefan says: NO
  • or should the file be listed as depiction in the GeoJSON of the reference? Stefan says: NO
Suggestion from Stefan:
  • When accessing the reference from the API the files are listed as CRM relations (reference - refers to - file) anyway? If no, this should be implemented somehow.
Actions #1

Updated by Bernhard Koschiček-Krombholz almost 5 years ago

  • Category changed from Backend to API
Actions #2

Updated by Alexander Watzinger almost 5 years ago

  • Target version changed from 5.0.0 to 204
Actions #3

Updated by Bernhard Koschiček-Krombholz almost 5 years ago

  • Tracker changed from Bug to Question
  • Assignee changed from Bernhard Koschiček-Krombholz to Stefan Eichert

Are image file reference relation equaly to e.g. actor file relations? (They are referenced inverse, so should we use them for depictions?)

Actions #4

Updated by Alexander Watzinger over 4 years ago

  • Target version changed from 204 to 5.0.0
Actions #5

Updated by Alexander Watzinger over 4 years ago

Is this still relevant and/or important for the 5.0.0 release? Delete if not relevant anymore, otherwise please comment.

Actions #6

Updated by Bernhard Koschiček-Krombholz over 4 years ago

It is relevant, if not for the 5.0.0 version, then for the next version.

Actions #7

Updated by Alexander Watzinger over 4 years ago

  • Subject changed from API Problem with References and Files to API - issue with references and files
  • Description updated (diff)
  • Category deleted (API)
  • Priority changed from Normal to 3

@ Berni: thanks for feedback it helps with the release. I expanded the description to a question that Stefan might be able to answer.

@ Stefan: now it's officially your ticket ;) in case this question can't be answered easily please move it to the next target version and we look at it together when we get the chance.

Actions #8

Updated by Stefan Eichert over 4 years ago

  • Description updated (diff)
  • Assignee changed from Stefan Eichert to Bernhard Koschiček-Krombholz

Dear all,
I created a wiki entry to document the files and reference topic.
https://redmine.craws.net/projects/uni/wiki/Model_and_concept#References-and-files

I hope this answers the question. Please check and close the ticket if this answers the question.
best, Stefan

Actions #9

Updated by Stefan Eichert over 4 years ago

  • Description updated (diff)
Actions #10

Updated by Bernhard Koschiček-Krombholz over 4 years ago

  • Status changed from In Progress to Closed

Dear Stefan,

Thank you for your answer. Since it is the normal behavior, that the file of a reference is in relations, everything will stay how it was.

Actions #11

Updated by Alexander Watzinger over 4 years ago

  • Category set to API
  • Target version deleted (5.0.0)

Thanks both for clearing that up.

Actions

Also available in: Atom PDF