MEDIUMIMAGESIZE - Detailed description

Overview

Parameters:MEDIUMIMAGESIZE
Category: Imaging (Image Processing)
Default value: 800x600
Product: eTASK.Other (Imaging)

What does this parameter do?

This parameter defines the dimensions for medium-sized image versions that are automatically generated when photos or images are uploaded to the eTASK.FM portal. The system saves each uploaded image in three different sizes (small, medium, large) and displays the appropriate version depending on the context.

The medium image size is frequently used in list views, overviews, and detail pages where a good balance between image quality and loading time is required.

What is this parameter used for?

• Automatic creation of medium-sized image versions upon upload

• Optimizing load times on overview pages and lists

• Providing balanced image quality for typical use cases

• Reducing storage requirements compared to original images

• Use in document management (table Gl_Dokumente_T, field Foto_Mittel)

• Image conversion via the admin tool DocumentImageConverter.aspx

Technical details (for administrators)

Format: String in the format <Breite>x<Höhe> (e.g. 800x600)
Default value: 800x600

Valid values:
- Format: <Breite>x<Höhe> (both values in pixels)
- Examples: 640x480, 800x600, 1024x768
- Width and height must be positive
integers - The "x" between the values is a lowercase letter

Important notes:

• This parameter is used when uploading images to create the medium-sized version

• Image conversion occurs automatically in the background

• The system reads the parameter from the database table GL_PROJEKT_KONFIGURATION_T (Type: IMAGING)

• If the format is invalid, the default value 800x600 is used

• The medium image version is stored in the Foto_Mittel of the table Gl_Dokumente_T is saved

• A subsequent change to the parameter only affects newly uploaded images

• Existing images can be DocumentImageConverter.aspx

Interaction with other parameters:

• SMALLIMAGESIZE: Defines small image version (default: 200x150)

• LARGEIMAGESIZE: Defines the large image version (default: 1600x1200)

When should you change this value?

Reduce the value (e.g., to 640x480) if:

• Storage space is limited and many images are being uploaded

• Network bandwidth is limited (slow internet connection)

• Mobile users need faster loading times

• Image quality is less important than performance in overviews

Increase the value (e.g., to 1024x768 or 1280x960) if:

• High-resolution monitors are in use

• Detailed image display is desired in overviews

• Sufficient storage space and bandwidth are available

• Image quality takes priority over loading speed

Leave 800x600 (default) if:

• The balance between quality and performance is optimal

• There are no special requirements

• Typical office monitors (Full HD) are used

• Standard use cases are to be covered

Important Notes

1. Note the
   aspect ratio This parameter specifies only the maximum width and height. The system scales images proportionally so that the original aspect ratio is preserved. A portrait-oriented photo (e.g., 3000x4000) is scaled to 450x600, not distorted to 800x600.

2. For new uploads only
   A change to this parameter affects only future image uploads. Medium-sized images already stored retain their previous size.

3. Retroactive conversion possible
   Using the admin tool DocumentImageConverter.aspx , all existing images can be reconverted using the new parameters. This may take several hours for large numbers of images.

4. Three-size system
   The portal always uses three image versions: Small (SMALLIMAGESIZE), Medium (MEDIUMIMAGESIZE) and Large (LARGEIMAGESIZE). Make sure the sizes are appropriately scaled.

5. Calculate storage requirements
   A medium image version with 800x600 pixels typically requires 100–300 KB of storage (depending on JPEG compression). For 10,000 images, this amounts to 1–3 GB for medium versions alone.

6. Format validation
   If the format is invalid (e.g., 800-600, 800*600, missing number), the system automatically uses the default value 800x600 without an error message. After making changes, check whether the desired size is actually being used.

Security

Does changing this parameter affect security?

No, this parameter has no direct security implications.

• No impact on access control or permissions

• No processing of sensitive data

• No network communication or external interfaces

• No authentication or encryption functions

Indirect considerations:

• Denial-of-service risk: Extremely large values (e.g., 10000x10000) could lead to memory or CPU overload during mass uploads. Recommendation: Keep maximum values below 2000x2000.

• Storage space management: Values that are too large increase storage requirements, which can lead to a shortage of space in the long term.

Data protection assessment:

• The parameter itself does not store any personal data

• Uploaded images may contain personal data (photos of people)

• Image size has no impact on GDPR compliance

• Access permissions for images are controlled by other systems

Conclusion: No security risks. Purely technical configuration for image processing.

Practical example

Initial situation:
A facility management company primarily uses eTASK on mobile tablets with limited internet bandwidth. Technicians upload photos of maintenance work daily. The default setting 800x600 results in long loading times in the mobile view.

Configuration:

After the change:

• Newly uploaded photos are saved as a medium version with a maximum resolution of 640x480 pixels

• The file size per medium-sized image drops from ~250 KB to ~150 KB

• List views with 20 images load 2 MB instead of 5 MB

• Mobile users experience 40% faster loading times

• Existing 5,000 images retain their previous size (800x600)

Optional - Retrospective conversion:

• Administrator opens DocumentImageConverter.aspx the admin area

• Selects "Reconvert all images"

• The system converts all 5,000 images to the new size (duration: approx. 2 hours)

• Storage savings: approx. 500 MB for medium-sized versions

Result:
Significantly improved performance for mobile users with acceptable image quality. The reduction from 800x600 to 640x480 is barely noticeable in list views, but saves a considerable amount of bandwidth.

Alternative scenarios:

Scenario A - High-resolution monitors: - Company upgrades to 4K monitors - Standard 800x600 appears pixelated in large overviews - Increase to 1280x960 for better display - Storage requirements increase by a factor of 2.5, but this is acceptable

Scenario B - Real estate management with architectural photos: - High-quality building photos should be displayed in rich detail - Increase to 1600x1200 (same value as LARGEIMAGESIZE) - Medium and large versions are identical - Saves storage space, as only two versions are needed instead of three

Recommended setting

For standard installations:800x600(balanced quality and performance)

Reason: - Proven standard for Full HD monitors (1920x1080) - Good balance between image quality and file size - Suitable for typical use cases (overviews, detailed views) - Average file size: approx. 150–250 KB per image (JPEG) - Fast loading times even with an average internet connection

Exceptions:

Mobile-first environments:640x480 - Many field staff using tablets/smartphones - Limited mobile data bandwidth - Performance is more important than maximum image quality

High-end environments:1024x768 or 1280x960 - Large-format 4K monitors in use - Fast network infrastructure (Gigabit LAN) - Sufficient storage space available - Image quality is a high priority (e.g., real estate management, architecture)

Storage-critical environments:640x480 or smaller - Database storage is expensive or limited - Very large volumes of images (>50,000) - Backup times should be minimized

Tip: After making the change, monitor the actual file size of some newly uploaded images. If necessary, you can make adjustments without affecting existing images.