#1303 proposal for two new <ocrstate> configurations

[Rodrigo Pozzebon]

Hello,

I would like to suggest a feature to enable better configuration management in our organization.

Our current work policy allows users to decide whether to use OCR or not. We want to encourage OCR usage without forcing it permanently. To achieve this, during installation, I would like to set OCR as ENABLED by default while still allowing users to make their own choices during NAPS2 usage.

I currently accomplish this in a labor-intensive way by manipulating the config.xml file for each user profile during installation.

To simplify this, I suggest adding 2 new values to the <ocrstate></ocrstate> element in appsettings.xml:

1. FirstRunUserConfig: In this configuration, if it is the user’s first time opening NAPS2, the default state defined in appsettings.xml (e.g., enabled) will be applied automatically. After that, the user can modify the OCR settings according to their preferences, and these changes will be saved to their profile for future sessions.

2. SessionUserConfig: In this mode, the user can change the OCR option during the current session, but upon reopening NAPS2, the configuration defined in appsettings.xml is automatically reloaded (overriding the user’s choices). This ensures the organizational default prevails while allowing temporary flexibility. This option would be ideal for our organization’s current needs.

Would this change be feasible?

Thank you!

---

config.xml applied to all users today via script

<?xml version="1.0" encoding="utf-8"?>
<UserConfig>
  <KeyboardShortcuts />
  <HasBeenRun>true</HasBeenRun>
  <Version>3</Version>
  <EnableOcr>true</EnableOcr>
  <OcrLanguageCode>por</OcrLanguageCode>
  <OcrMode>Fast</OcrMode>
  <OcrAfterScanning>true</OcrAfterScanning>
</UserConfig>