Hi Naoki,

This is indeed a scenario where ISHRemote could work. In between meetings I came up with the following code construct, it highlights the cmdlets you need and hopefully sets you off in the right direction to comply with your custom setups and rules.

The below cmdlet takes a full folder path, gets the content filtered to only "Low" resolution images and drops them in the C:\Temp\20200708  folder of the system running ISHRemote.

Get-IshFolder -FolderPath "\General\Planning\Scalability\Images" |
Get-IshFolderContent -MetadataFilter (Set-IshMetadataFilterField -Level Lng -Name FRESOLUTION -FilterOperator Equal -Value "Low") |
Get-IshDocumentObjData -FolderPath C:\temp\20200708

The result in C:\temp\20200708 looks like

basic infoshare installation (vpn)=GUID-A4476B47-350E-4C19-9E8F-F02504568741=1=en-us=Low.jpg
basic infoshare installation with one firewall=GUID-73457A06-E9DB-4574-BB20-79C3358513A7=1=en-us=Low.jpg
basic infoshare installation with two firewalls=GUID-A48C942E-FD85-4776-A104-8AD6AF439772=1=en-us=Low.jpg
basic infoshare installation=GUID-A5B24B14-F0C1-4C18-B33B-6B1C8ED8A6C1=4=en-us=Low.png
batch server configuration=GUID-2AD51EE7-F90A-409A-9570-65542A99CA67=3=en-us=Low.png
component load balancing=GUID-D5C3D15F-785E-471F-A051-96B943FBCE48=3=en-us=Low.png

Best wishes,
Dave

Hi Dave,

Since we assigned special prefixes to image objects, I realized that I can use Find-IshDocumentObj instead of Get-IshFolderContent. I thought out following code and it satisfied our needs.

# image_download.ps1 <PUBID> <download_folder_path>
Param($pubid, $download_folder_path)
$resolution = "Edited"
New-IshSession -WsBaseUrl https://XXXXXXXXXX/ISHWS/ -IshUserName XXXXX -IshPassword XXXXX
Find-IshDocumentObj -IshTypeFilter ISHIllustration -MetadataFilter (Set-IshMetadataFilterField -Level Logical -Name FTITLE -FilterOperator Like -Value $pubid),(Set-IshMetadataFilterField -Level Lng -Name FRESOLUTION -FilterOperator Equal -Value $resolution) | Get-IshDocumentObjData -FolderPath $download_folder_path

Again, thank you for your suggestion, Dave.

Best regards,

Naoki

Yep the Find-IshDocumentObj works if you can filter enough. There is a risk of course that if you don't filter enough that you are pulling millions of objects to your ISHRemote client and in turn trying to load them in memory (or probably out-of-memory)

This is one of the reasons that I started implementing the https://github.com/sdl/ISHRemote/milestone/9?closed=1 changes like above -MetadataFilter on cmdlet Get-ishFolderContent as iterating folder is by itself a nice way to break the data problem in smaller chunks (read folders :-) )

-Dave

Yep the Find-IshDocumentObj works if you can filter enough. There is a risk of course that if you don't filter enough that you are pulling millions of objects to your ISHRemote client and in turn trying to load them in memory (or probably out-of-memory)

This is one of the reasons that I started implementing the https://github.com/sdl/ISHRemote/milestone/9?closed=1 changes like above -MetadataFilter on cmdlet Get-ishFolderContent as iterating folder is by itself a nice way to break the data problem in smaller chunks (read folders :-) )

-Dave