Question #1142
closed
API - issue with references and files
Added by Bernhard Koschiček-Krombholz about 4 years ago.
Updated about 4 years ago.
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.
- Category changed from Backend to API
- Target version changed from 5.0.0 to 204
- 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?)
- Target version changed from 204 to 5.0.0
Is this still relevant and/or important for the 5.0.0 release? Delete if not relevant anymore, otherwise please comment.
It is relevant, if not for the 5.0.0 version, then for the next version.
- 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.
- Description updated (diff)
- Assignee changed from Stefan Eichert to Bernhard Koschiček-Krombholz
- Description updated (diff)
- 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.
- Category set to API
- Target version deleted (
5.0.0)
Thanks both for clearing that up.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by