View original file without download + open

[fisketjon]

Is there a way to view the full size image file without having to use download?

[Mario]

I assume you mean in IMatch Anywhere WebViewer?

Access to the original RAW or other original assets is done via downloading the original (if your permissions are sufficient). Browsers cannot display RAW files, many video formats, Office documents or other digital assets.

[fisketjon]

Yes, I mean the WebViewer, but I was not thinking of RAW files. In fact I was hoping that I could exclude RAW files of any type as well as TIF files from the WebViewer. 

I just wanted to have an easy way for the user to zoom into the full size jpg file ("pixel peeping") 

[Mario]

The maximum size you can zoom into is determined by the cache image size configured. If the Admin configures a 100% cache image size, you'll get a 100% preview. The user account IMWS runs under must be able to access the original images. Ask your It people about this and if you admin yourself, see the IMA Admin documentation for detailed information.

[fisketjon]

I've defined ORIG with long edge 0px, and changed the Viewer to use this image size.

However, when I click on an image to display it, the image looks as if the thumbnail has been resized to fill the window instead of showing the original.

Inspect shows this

http://NFSERVER:8081/v1/files/image?auth_token=2d6b114bcff81a0f1d2a5925eb5bb2edb0840e7be9e70fc0511c06701cf27daa&id=167024&imagesize=ORIG&default=true

[Mario]

However, when I click on an image to display it, the image looks as if the thumbnail has been resized to fill the window instead of showing the original.

The typical reason for this is that IMWS cannot access the original image and falls back to using the thumbnail.
If the images managed by IMWS are not on the same computer IMWS runs on, you must create/run IMWS under a user account that can access the other computer.

See the section Accessing Files or Databases on Different Computers (Servers, NAS) in the IMWS help for detailed information.

[fisketjon]

Setting a long edge at 8000 works and gives me a detailed image, but long edge at 0 gives me a pixelated image.

I have given my own user the ability to logon as a service. The image files are on the same PC as the IMWS is installed on.

[Mario]

The documentation states:

Long Edge The long edge for the cache image size. Allowed sizes are between 40 and 10000 pixels.
The special value 0 means original image size but should only be used under very specific circumstances.

Probably you should stick to the 40 to 10000 value for long edge.
Note that this does not give access to the original image, just a larger cache image produced from the image file.

I have not worked on the cache system in IMWS for several years, it just works.
I'm not sure about the special circumstances for the 0 edge value. Probably something I've added at the request of an institutional user at the time...

[fisketjon]

Browser (Chrome) show some error messages

http://nfserver:8081/v1/idlist?auth_token=5840091fad2774366f8dbe2c2ce1b88692de4cf1e749be19843257119e623b1c&name=idlist.likes.FDC0F37C-8771-43DE-914D-EAB8A405A4D1.default&valacl=true&validate=file

http://nfserver:8081/v1/data?auth_token=5840091fad2774366f8dbe2c2ce1b88692de4cf1e749be19843257119e623b1c&name=imatchSettings_fl_config

http://nfserver:8081/v1/data?auth_token=5840091fad2774366f8dbe2c2ce1b88692de4cf1e749be19843257119e623b1c&name=imatchSettings_fl_history

http://nfserver:8081/v1/data?auth_token=5840091fad2774366f8dbe2c2ce1b88692de4cf1e749be19843257119e623b1c&name=imatchSettings_fl_kw_favorities

http://nfserver:8081/v1/data?auth_token=5840091fad2774366f8dbe2c2ce1b88692de4cf1e749be19843257119e623b1c&name=imatchSettings_fl_cat_recent

http://nfserver:8081/imatchviewer/imatch/config/downloads.json?cbust=1753096906132

http://nfserver:8081/imatchviewer/bower_components/angular-i18n/angular-locale_nb-no.js

http://nfserver:8081/v1/data?auth_token=5840091fad2774366f8dbe2c2ce1b88692de4cf1e749be19843257119e623b1c&name=1752929280208.IMWS_DEFAULT_USER.undefined



You cannot view this attachment.

[Mario]

Just ignore. Your browser will for example automatically look for favicons, which may or may not exist in the requested format. And the server will return a 404 when the favicon does not exist, which is perfectly normal.

And when a settings does not exist, a 404 is returned. Perfectly normal. WebViewer handles that.

What is your intention with using IMWS?
Reverse-engineer it? Just use it?

[fisketjon]

As I haven't enabled Authentication yet in the WebService Controller I wonder if the Default user
IMWS_DEFAULT_USER should have been created. There is no such user on this computer.

[fisketjon]

Just ignore. Your browser will for example automatically look for favicons, which may or may not exist in the requested format. And the server will return a 404 when the favicon does not exist, which is perfectly normal.

And when a settings does not exist, a 404 is returned. Perfectly normal. WebViewer handles that.

What is your intention with using IMWS?
Reverse-engineer it? Just use it?

My intention was to have my family use it instead of BreezeBrowser.

Previously I have had tif / raw files (if one exist) in one folder (per month and camera), and jpegs in a subfolder. I have also kept a different set of ("display") folders with jpegs in fullhd size. If I go back and delete some old files ("cullng") it's a logistic nightmare to update the "display" folders since they are by month only and not split by camera.

Since not all photos have a raw file (either because the camera couldn't or the photographer opted to not use raw) there's a possible source of confusion and handling error (on my part). Having the raw (or scanned tif) and their corresponding jpeg files in the same folder makes it easier to avoid editing an original jpeg.

I would like to set IMWS up in a way that users can only see the jpg (or if the original is a jpeg and an edited version exists the edited jpeg). Now it displays just the RAW/TIF files or both the RAW/TIF and the JPG files.

If I can't have a simple way for others to view the photos with the selection possibilities in IMWS it takes away some of my motivation to do the work of categorizing the photos.

[Mario]

You have files in the same folder and you want to show only some of the files, or when a file in format A exists, show A but not B. That's quite a specific requirement...

Do you use versioning? You write

Having the raw (or scanned tif) and their corresponding jpeg files in the same folder makes it easier to avoid editing an original jpeg.

This means that the JPG would be a version of the RAW or TIF. And it would be hidden in the version stack when the version stack is collapsed. Or you make the JPG the master, and the TIFF/RAW the version. Then the JPG becomes the stack top when there is a version stack. Else the JPG will just be on itself and not form a version stack.

IMatch Anywhere WebViewer can handle stacks, showing only the stack top. Which is, in your case, the JPG. If there is only JPG, it is shown as is. If the JPG has versions (RAW/TIFF) the versions are hidden and only the JPG is visible, because it is the version stack master/top.

See File Relations: Versioning for more information.

[fisketjon]

You have files in the same folder and you want to show only some of the files, or when a file in format A exists, show A but not B. That's quite a specific requirement...

Maybe it is, but I just want them (my family) to see the finished photo (not the digital "negative")

I have set up versioning, but appearantly I should have made the jpeg's the master which is kind of the opposite of what I think of when I hear the word "master".

Anyway, is there a way to switch them so that master becomes version and vice versa?

[Mario]

Anyway, is there a way to switch them so that master becomes version and vice versa?

Simple. Delete the old rule and add a new rule, this time making the JPG the master and the other files the version.
This should be a workable solution for your particular requirement (only ever show the JPG). The users also must enable the option to hide stacked files (on by default, when I recall correctly).

Another venue would be ACLs based on a category. Add all files you want to hide to this category, and add an exclusion for that ACL to the group containing your users. See the IMA documentation for more information about access control and ACLs.