Images best practise

ThorstenvBW

on other systems (soory) file management and storage are optionally on and S3 kind of infrastructure but still managed by the systems access rights (directus for example) ... is this a direction suitable for Rei3 ??

gabriel

ThorstenvBW on other systems (soory) file management and storage are optionally on and S3 kind of infrastructure but still managed by the systems access rights (directus for example) ... is this a direction suitable for Rei3 ??

Sorry, but please take the time to write out your thoughts. I can barely follow, if you are asking about a storage integration or API connector or something else. What do you want to achieve?

gabriel

ThorstenvBW Since an external website needs to access the data in Rei3 (REST) there has to be some way to read the images.

The integrated r3 API feature can fulfill this requirement. When you create a GET API and include a files attribute, you get a list of all files (a JSON array). This list includes meta data (file name, size, hash, ID) for all files. To get the files out of r3, you can then use the generic download handler ( /data/download). For both getting the files list (via API) and downloading files (via the handler), you need to execute an API auth call first.

The process would be:

Authenticate via REST auth call, get auth token as response
Receive files list via REST GET call
Parse file IDs from files list
Download desired files via download handler (the same URL that you would use when downloading files from within r3, just with different file IDs and a current auth token, s. step 1).

ThorstenvBW

gabriel GREAT that's the info i was looking for Thanks. (could not find that in docs ... )

Using this i can make make usage of an CDN for external use (website) of the images .
To claryfy: data is not only available on the companys website but also on big listings. So hits on images can be huge and if a CDN can handle that would offload the REI3 server.

Thanks

gabriel

ThorstenvBW another (but somehow awkward) possibility could be to import and export the images ?
as soon as the images are imported en the records are saved, some naming convention is applied and so on the Images are the exported to a external acessible location ?

As explained above, you can import files via the import functions, as long as you know the file names. If you want to import files via REST, you need to wait for r3.12 which will officially support uploading files via REST. Going this route in r3.12, you would upload files via the generic upload hander (/data/upload), receive file IDs as response and then attach the files to new or existing records via a regular r3 API POST call.

Exporting images also works via the export functions - but just as well via a REST GET call (to get the file meta data) and then download call (to get the files) - s. my post above. This already works in r3.11.

ThorstenvBW

gabriel Good to know !!

ThorstenvBW

gabriel ThorstenvBW on other systems (soory) file management and storage are optionally on and S3 kind of infrastructure but still managed by the systems access rights (directus for example) ... is this a direction suitable for Rei3 ??

Sorry, but please take the time to write out your thoughts. I can barely follow, if you are asking about a storage integration or API connector or something else. What do you want to achieve?

Your answers cover this ... My main concern was offloading the REI3 instance from massive filehandling / serving images.
if there was a "S3" connector then external systems could access data (filename) via rest and for image serving could ask the S3 instance ....
This way i would not need the export step considered above (in order to make the images/ files available via CDN (content delivery network)

i hope this claryfys my question
and again thanks for the insights !!!

ThorstenvBW

if the file object could have an internal sort info and an primary tag ... that would help immensly !! (request?)

ThorstenvBW

ThorstenvBW "if the file object could have an internal sort info and an primary tag ... that would help immensly !! (request?)"
I want to elaborate on this:
when holding 50 images for one entity som "filehandling" is required and i somehow look at Album management on my phone ...

flagging an image as primary of Albumcover is very useful in internal and external (webites / apps) listings showing always the most important image of all
sorting (a sortfield as number for example (1,2,3,4,5,100,200) could further draw on the same idiea but is more elaborate to incorporate (i guess) and to handle.
sorting on filename (camera's use order in filenames) is available already ?!
same for dates ?!
I think especially with a primary flag the image container would be much more useful (also to listings in Rei3) not only externally
(i did some "system tweaking") to accomplish those things : adding a leading 0 to the filename sorts that file as first in the gallery view, great but!! in a list form limiting the image container to 1 picture does not apply that sorting ... here order of import takes precedence ... a primary flag would fix this simpel en efficiently ?!)

gabriel

ThorstenvBW if the file object could have an internal sort info and an primary tag ... that would help immensly !! (request?)

Sorry, this would require a major rework of the file backend. Nothing that can be done without a major internal project and a corresponding priority.

gabriel

ThorstenvBW when holding 50 images for one entity som "filehandling" is required and i somehow look at Album management on my phone ...
flagging an image as primary of Albumcover is very useful in internal and external (webites / apps) listings showing always the most important image of all
sorting (a sortfield as number for example (1,2,3,4,5,100,200) could further draw on the same idiea but is more elaborate to incorporate (i guess) and to handle.
sorting on filename (camera's use order in filenames) is available already ?!
same for dates ?!
I think especially with a primary flag the image container would be much more useful (also to listings in Rei3) not only externally
(i did some "system tweaking") to accomplish those things : adding a leading 0 to the filename sorts that file as first in the gallery view, great but!! in a list form limiting the image container to 1 picture does not apply that sorting ... here order of import takes precedence ... a primary flag would fix this simpel en efficiently ?!)

Please have a look at how r3 manages files by creating your app and looking at the file data structures that you get when you run GET requests. There is some meta data available, that you can use for sorting - like the file name or change dates.

Cover images you can address, by using a separate files attribute.

For a cover image, it is also possible to use a different/fixed file name in the files list. This could be used by your endpoints that serve the files via CDN; although r3 internally would just treat it as a regular file. But I would need to get familiar with what you are planning to say anything more.

In general, r3 was not really built for such a scenario. It is primarily designed for internally accessed business apps, less for hosting large image galleries for public consumption. That does not mean that we cannot do it - but it might be necessary to add more features to r3 to enable such use cases. If you are planning to use r3 for your business, you can get in touch with us and we could discuss your requirements and how much effort new features would be to implement. Many organizations have sponsored features in r3 to fulfill new requirements - and still save money in the process.

ThorstenvBW

gabriel Sorry, this would require a major rework of the file backend. Nothing that can be done without a major internal project and a corresponding priority.

Yes now i get the quote system (-:

Ok, too bad ... but i understand

ThorstenvBW

gabriel Sorry, this would require a major rework of the file backend. Nothing that can be done without a major internal project and a corresponding priority.

i gather the framework already carries some meta data (in JSON)? like dates, versions, filenames (origina).
So if we could carry one more variable (bool) for "primary" ?
In the gui it woild just be a tiny checkbox in the existing frame
problem is to keep track of the "primary's" since only one of the images may carry the true value ... thats a thing i guess.
Just braining away sorry (-:

ThorstenvBW

gabriel In general, r3 was not really built for such a scenario. It is primarily designed for internally accessed business apps, less for hosting large image galleries for public consumption. That does not mean that we cannot do it - but it might be necessary to add more features to r3 to enable such use cases. If you are planning to use r3 for your business, you can get in touch with us and we could discuss your requirements and how much effort new features would be to implement. Many organizations have sponsored features in r3 to fulfill new requirements - and still save money in the process.

Yes absolutely. Now its a one off but i certainly consider this if a business growth out of it !

ThorstenvBW

gabriel Cover images you can address, by using a separate files attribute.

That is an option but somewhat awkward ...
in the flow of things the broker just wants to upload a bunch of images and be done with it

ThorstenvBW

gabriel It is primarily designed for internally accessed business apps, less for hosting large image galleries for public consumption.

Got it but my system is two fold. Rei3 serves as Business App. But the result of this "business" or better the created content therein has to become public ie. own website but also Internet listings / yellowpages / speciality sites.
Therefor in my cas i need the uploaded images in a public space.
best would be just to serve out of the /data/ directory, or, for security, keep a copy of the /data/images dir somewhere acessible ... seems much easier than do import and export steps ... but okay

ThorstenvBW

gabriel Please have a look at how r3 manages files by creating your app and looking at the file data structures that you get when you run GET requests. There is some meta data available, that you can use for sorting - like the file name or change dates.

not shure what you mean. Any docu on this ?
i see the data/download/ url with variables yes ... and ik know there is sorting on dates and filenames ... but not how to access that in detail ...
any hint ?
Thanks

gabriel

ThorstenvBW Got it but my system is two fold. Rei3 serves as Business App. But the result of this "business" or better the created content therein has to become public ie. own website but also Internet listings / yellowpages / speciality sites.
Therefor in my cas i need the uploaded images in a public space.
best would be just to serve out of the /data/ directory, or, for security, keep a copy of the /data/images dir somewhere acessible ... seems much easier than do import and export steps ... but okay

For this case, it´s probably best to use 2 systems: One internally (like r3) and another externally. r3 is ill-equipped to handle the later. From what you describe, you are already doing/planning this.

gabriel

ThorstenvBW i gather the framework already carries some meta data (in JSON)? like dates, versions, filenames (origina).
So if we could carry one more variable (bool) for "primary" ?

Tools like r3 are complicated beasts. All this abstraction, necessary to make them low/no code tools in the first place, means that changes like this are complex and have many consequences. We do regularly add new features for organizations to meet niche requirements - but these changes take days, so it´s not always worth it to spend for the effort.

gabriel

ThorstenvBW not shure what you mean. Any docu on this ?
i see the data/download/ url with variables yes ... and ik know there is sorting on dates and filenames ... but not how to access that in detail ...
any hint ?

What I mean is what I described in my posts above. The download handler data/download is just for downloading files. To deal with file meta data, you need to have an API defined in your app that includes a files attribute. Once you have this API, you can then execute GET requests and see the data structure and what information is included.