2. Improvements/Features/Changes 
add chapter

2.1 Import/Export Scanprofiles 
add section

The scanprofiles are included when BCS-2 settings are exported, so that they do not have to be recreated after a new installation of  BCS-2. Prerequisite for the usage is the connection to the same scanner with which the profiles were created. (RM#4382), 

2.2 Save user name with the job 
add section

In the basic tab of each workflow, it is possible to activate/deactivate, if information to the logged-in windows user (ut.userName()) is stored in the jobs. When the function “Save user name: if active, save username in job structure:” is active following information is stored in each job:  

  • Username of the person that created the job 
  • Username of the person that last changed the job 

The data can be used to 

  • Filter the job list and only show the jobs of the logged in user  
  • Show the username in the job list 
  • Output the information via the ReportSuite 

The function is deactivated by default. (RM#4284) 

2.3 Filter job list for logged in user 
add section

When the workflow function “Save user name: if active, save username in job structure:” is activated, a filter for the jobs in the job list can be used.  

Through the activation of “filter jobs based on users” in the basic tab of the settings only the users own jobs are displayed on the list. (RM#4287) 

2.4 Save Scan Profile of the job 
add section

When working with scan profiles, the last scan profile that is used in a job is saved in the job information when the job is closed.  

If the job is reopened BCS-2 checks if a scan profile was saved for the job and selects it. If the scan profile was deleted the user is notified. Scan Profiles can also be displayed in the job list. . (RM#3821)  

2.5 Display scan profile in the job list 
add section

The last used scanprofile can be view in the job list. The additional column can be defined in the settings tag “job list“. The variable is called job.scanProfile and can be selected via the “select variables”. (RM#3820).  

2.6 Only load camera SDK when camera is used 
add section

The loading of the camera SDK can be activated/deactivated in the General Settings/Scanner Settings –  Scanner Selection “Activate loading camera SDK” . The function must be active if cameras are to be used. The function is deactivated by default.  (RM#4402) 

2.7 Job List – Unload BCS-2 job via the job list 
add section

The function “unload job into file” can be used via the job list for one or multiple jobs.  ( RM#4401)  

2.8 Transfer Target – Unload BCS-2 job 
add section

The unloading of a BCS-2 job can now also be done via a transfer target. A new transfer target type “Unload JobFolder” was implemented. The corresponding job with all job data (scans, indexes, metadata, masks) is copied to a file. The job can be imported in the same or another BCS-2 station. (RM#4191)  

2.9 SONY ILX-LR1 
add section

The connection to the industrial camera SONY ILX-LR1 via the SONY SDK was implemented, so that the camera can be used like the CANON EOS cameras to scan with BCS-2.  (RM#4165).  

2.10  Connection to Microsoft OneDrive 
add section

Microsoft OneDrive can now be used fby BCS-2 as a local drive. OneDrive can be selected during the installation or subsequently for the Data directory/ Scandata. The usage of one drive as a transfer target ist also supported.  (RM#4256) 

2.11 Connection Zeutschel OS15000 
add section

The Zeutschel OS15000 can be operated by BCS-2 via the 64-Bit TWAIN driver. For easier operation the control of the glass plate by BCS-2 was implemented.   

2.12 Integration CANON EDSK V13:18 
add section

Through the integration of the CANON EDSK V13.18 newer Canon models such as EOS R5 are now supported by BCS-2 in addition to models such as EOS 5DS, EOS 5DS R, EOS 760D, EOS 750D und EOS M3. 

2.13 Modification of the transfer type eL- export Replacement of the IWCOCR format through the ALTO format
add section

V3.8 of the MyBib eL (electronic reading room) can use ALTO files. The necessity to create “IWC-OCR  files” is no longer given. For this reason, the eL export format in BCS-2 was changed so that BCS-2 automatically transfers Alto files into the eL Zip file, which can then be transferred to the reading room and checked in.  (RM#4379). 

2.14 Unload BCS-2 jobs – Unload jobs into file 
add section

The function “Unload Job in file“, which can be found in the tab “Job” was modified. The corresponding job including all job Metadata  (scans, indexes,etc.) are no longer placed into a zip file, but are copied to a file. The unloaded job can later be loaded into the same or a different BCS-2 containing the workflow of the job. The filename consists of the job number, date and time (RM#4398, RM#4399) 

2.15 Import BCS-2 job 
add section

The jobs which were unload into files can be imported.  (RM#4400 )