GS1 Logger. User Manual Guide

Transcription

1 GS1 Logger User Manual Guide Release 2.2, Proved, August 2016

2 Document Summary Document Item Document Name Current Value GS1 Logger User Manual Guide Document Date August 2016 Document Version 2.2 Document Issue 1 Document Status Document Description Proved User Manual Guide Contributors Name Fruzsina Ábrahám Dávid Kétszeri Zsolt Bócsi Organisation GS1 Hungary GS1 Hungary GS1 Hungary Log of Changes Release Date of Change Changed By Summary of Change Fruzsina Abraham draft Fruzsina Abraham proved Fruzsina Abraham BQ webservice, BQ uploads, GS1 Logger rename Edit Aigner taking useable pictures Disclaimer GS1, under its IP Policy, seeks to avoid uncertainty regarding intellectual property claims by requiring the participants in the Work Group that developed this GS1 Logger User Manual Guide to agree to grant to GS1 members a royalty-free licence or a RAND licence to Necessary Claims, as that term is defined in the GS1 IP Policy. Furthermore, attention is drawn to the possibility that an implementation of one or more features of this Specification may be the subject of a patent or other intellectual property right that does not involve a Necessary Claim. Any such patent or other intellectual property ri ght is not subject to the licencing obligations of GS1. Moreover, the agreement to grant licences provided under the GS1 IP Policy does not include IP rights and any claims of third parties who were not participants in the Work Group. Accordingly, GS1 recommends that any organization developing an implementation designed to be in conformance with this Specification should determine whether there are any patents that may encompass a specific implementation that the organisation is developing in compliance with the Specification and whether a licence under a patent or other intellectual property right is needed. Such a determination of a need for licencing should be made in view of the details of the specific system designed by the organisation in consultation with their own patent counsel. THIS DOCUMENT IS PROVIDED AS IS WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY, NONINFRINGMENT, FITNESS FOR PARTICULAR PURPOSE, OR ANY WARRANTY OTHER WISE ARISING OUT OF THIS SPECIFICATION. GS1 disclaims all liability for any damages arising from use or misuse of this Standard, whether special, indirect, consequential, or compensatory damages, and including liability for infringement of any intellectual property rights, relating to use of information in or reliance upon this document. GS1 retains the right to make changes to this document at any time, without notice. GS1 makes no warranty for the use of this document and assumes no responsibility for any errors which may appear in the document, nor does it make a commitment to update the information contained herein. GS1 and the GS1 logo are registered trademarks of GS1 AISBL. Release 2.2, Proved, August GS1 AISBL Page 2 of 59

3 Table of Contents 1 Introduction Overview of the user levels Registration Registration of GS1 Member Organisations Registration of Companies Registration of (MO or Company) Users Mobile application Login Forgotten password Change password Logout Settings Mobile App Data input Manual data input Automatic data input Scanning several data mediums Stringing Validation Taking usable pictures is the basis of reports How not to make reports Qualification List of History Mylogger website List My prefix Translation Statistics Statistics sub-pages How to use the Admin website Activate a new company registration Edit company data Edit users data Batch query How to use BQ webservice History of queries Contacts Release 2.2, Proved, August GS1 AISBL Page 3 of 59

4 1 Introduction Starting from July 2015 GS1 Member Organisations are able to register and manage their user companies in the GS1 Logger System. Therefore you, as a GS1 MO can provide GS1 Logger as a service to your user companies. Consequently your user companies will get access to the following main functions: Quick verification and validation of barcodes and GS1 ID Keys with the Logger mobile application (available on Android, ios and Windows Phone 8) History of records and statistics on the Logger website ( Batch Query verification and validation of GS1 ID Keys in high amounts on the LFS website by uploading the list in excel sheet formator an automatic machine-to-machine Batch Query webservice is also available Admin website in order to manage their users Release 2.2, Proved, August GS1 AISBL Page 4 of 59

5 2 Overview of the user levels There are 4 levels of users in the GS1 Logger system. The following figure shows the hierarchy of users. System Administrator GS1 MO Supervisor Company Supervisor Company User GS1 MO User GS1 MO Report Administrator User System Administrator GS1 MO Supervisor Company Supervisor GS1 MO user Company user GS1 MO Report administrator Tasks and rights Manages and supports the registration of GS1 Member Organisations. The person at a GS1 MO who manages the access rights of the MO users and companies and can edit the user data on the Admin website. The MO Supervisor can see all the records of the users below his/her level (MO users, Company users). The person at a registered company who manages the access rights of the company s users and can edit the user data on the Admin website. The Company Supervisor can see all the records of the users below his/her level (Company users). GS1 MO users and Company users have the same rights can see only their own records on the mylogger website (stafflogger.gs1hu.org). The GS1 MO Report administrator is an MO user with additional rights. The Report administrator is the addressee of the Logger reports and is in charge of the follow-up of invalid ID Keys reported by other users. Release 2.2, Proved, August GS1 AISBL Page 5 of 59

6 3 Registration 3.1 Registration of GS1 Member Organisations If your MO is not registered yet in the Logger System, you can initiate the registration on the following website: 1. Fill in the MO registration form a. Select your MO s name from the dropdown list b. Provide the username and address of the MO Supervisor c. You can provide a different colleague as Report Administrator by checking in the [Different report administrator] checkbox. If this checkbox is not ticked off then the MO Supervisor will be also the Report Administrator of your MO. 2. After pressing the [Register] button an automatic will be sent to the Logger System Administrator, who will check the data provided on the registration form. 3. If the form was completed correctly the System Administrator will approve your MOs registration and send a notification about the completed registration to the MO Supervisor and Report Administrator. 4. The MO Supervisor will also receive the MO s verification code that is needed for your colleagues to register as users of your MO. This ensures that only those people can register in the system as your users who know your MO s verification code. Business Process GS1 MO registration GS1 MO Supervisor Start registration Filling in the MO registration form Receiving notification about the completed registration process End of MO registration LFS system Sending notification about the new registration about the registration End of MO registration System Administrator about the new MO registration Register the MO on the Admin website Sending notification to the GS1 MO Supervisor about the completed registration Always If Report Administrator is different from Supervisor Sending notification to the Report Administrator about the registration End of MO registration about the registration MO Report Administrator Receiving notification End of MO registration Release 2.2, Proved, August GS1 AISBL Page 6 of 59

7 3.2 Registration of Companies When a GS1 Member Organisation decides to give access to a user company the following steps should be taken. 1. Provide the registration website URL to the company: 2. The contact person at the company has to fill in the Company registration form. The company has to select the name of the GS1 Member Organisation at which it is registered as a GS1 User Company. a. If the GS1 MO is not on the dropdown list then the company i. should contact the MO to register in the Logger System OR ii. should select the GS1 Global Office from the dropdown list 3. An automatic will be sent to the relevant MO Supervisor about the registration. 4. The MO Supervisor checks the company data and if it is OK - approves the registration on the Admin website: 5. The MO Supervisor sends an to the Company Supervisor about the completed registration. The notification should contain the verification code of the company. Below you can find a recommended template of this . Subject: Welcome to GS1 Logger for Staff Body: Dear GS1 Logger for Staff Supervisor, Your company has been registered in the GS1 Logger for Staff system. The following verification code is required for online user registration: xxxxxx Please note that each colleague who would like to use the application needs to be registered on the following website: With the Supervisor account you will be able to see all scanned records by your colleagues on this website: Kind regards, MO Supervisor Release 2.2, Proved, August GS1 AISBL Page 7 of 59

8 Business Process Company registration Company Supervisor Start registration Filling in the Company registration form Receiving about the completed registration End of company registration LFS System Saving company registration information in the LFS database (with inactive status) Sending notification about the registration to MO Supervisor notification e- mail End of company registration GS1 MO Supervisor about company registration Activating company status on the Admin website Sending notification to the Company Supervisor End of company registration Release 2.2, Proved, August GS1 AISBL Page 8 of 59

9 3.3 Registration of (MO or Company) Users The users of a registered MO or company can register on the following website: Users have to request the MO/company verification code from their supervisors. This ensures that only those people can register on the Logger System as users of an MO/company who get access from the MO/Company Supervisor. Business Process User registration LFS System User MO / Company Supervisor Initiate registration Receiving request Request "verification code" from Supervisor Handing over the verification code to the requestor Receiving verification code Starting registration Filling in the user registration form Saving user data in LFS database End of user registration End of user registration Release 2.2, Proved, August GS1 AISBL Page 9 of 59

10 4 Mobile application 4.1 Login The registration button on the first screen of mobile client drives the user to the registration website of the GS1 Logger application. Users can use Logger with their own login name and private password by pressing the Login button. This guarantees that only users can access their own data and records. Server side authentication is independent of whether it is a registration of a web or a mobile client. Misspelled credentials can cause an authentication error. We also get an error message via the authentication process if the client version of the device is unsupported. After start-up, GEPIR Root XML, language resources and location resources get updated if there are new versions available on the server. Furthermore, there are some other checking functions running automatically e.g. internet access check. Release 2.2, Proved, August GS1 AISBL Page 10 of 59

11 4.2 Forgotten password Use this function in case you forget your password. 4.3 Change password Use this function if you would like to change your password. 4.4 Logout Use this function if you would like to log out. 4.5 Settings Mobile App GS1 Logger mobile application has a function, which allows further settings of location information related to ON-OFF position of the GPS of the device. Furthermore, this function also makes it possible that on the administration website we give limited location information about our location belonging to our record, while we can see the accurate coordinates on the website of the application. With GPS ON (default) coordinates setting, the current coordinates are transmitted to the server and the supervisor can see the very same information at our record. The two new characteristics related to the ON setting can modify this accuracy; for others instead of the current coordinates it shows the country or in the location database the smallest place. With GPS OFF the device won t be able to transmit coordinates, but we can modify it either with the default or by the selection of an area e.g. a country or a smaller area from a hierarchic list if there are more detailed information available. In the pre-set setting (default) the area of the country given in registration (the GLN identifier) will go to the OFF mode, thus such location information will be generated automatically to the record as if it were recorded in the registered country. The GPS defaults either ON or OFF exist only until users modify it, i.e. until they give other location information to be revealed themselves. With the GPS ON the active setting displayed on the main screen is green and with the GPS OFF it is red. In case the GPS is off, users receive a warning message after starting the application. In the course of setting GPS ON users have three options to give their location: Coordinates (default) Country Smallest Region By selecting of the first one, everybody will see the exact location of your scanning. The coordinates are transmitted in the two others as well, but the exact location is available only for the user, others will see only the selected level (country, smallest region). Release 2.2, Proved, August GS1 AISBL Page 11 of 59

12 GPS OFF is set from a hierarchical list of location. In most of the cases, the country is available. Further levels may be defined by the MOs in the future. 4.6 Data input After logging in, the main screen appears, on which we can input the GS1 identification number we would like to check. The data input can be done manually or by automatic scanning with the built-in camera of the device. Besides giving the GS1 identification number to be checked, the Validation, the Qualification, the New Log, the Add Photo, the History and the Settings functions can be accessed on the main screen. Before sending data, network connection will be checked. You have the possibility to send a record with picture(s) immediately or you can attach picture(s) after data transfer through the main screen, which showing the result of checking by pressing the Add photo button or at any time through the History Detailed Record Data screen to the record later on before reporting. Every cases there are three selectable types of picture sizes (small, middle, large). You can attach a maximum of three pictures to each record. By pressing the Send button, you can forward only the data of the record and the pictures attached. However, if you press the Send&Report button, after the aforementioned process, the report also will be sent. Afterwards, it isn t possible to attach further photos even through History Detailed Record Data screen to these records. Release 2.2, Proved, August GS1 AISBL Page 12 of 59

13 The Send&Report button is not active if a qualification error is found after the scanning. Another function is to add comments to your reports with these additional information you can help the work of the colleagues who are processing the invalid numbers Manual data input During the manual data input, first we have to select the necessary data type from the AI selector then we can enter the ID key. Manual data entry allows you to select only those AIs that are displayed on the AI selector field. Recording other types is not possible. The keyboard changes from numeric to alphanumeric automatically depending on the AI. The Done button also becomes active when the minimum number of characters has already been entered. Overtyping triggers a warning tone. Release 2.2, Proved, August GS1 AISBL Page 13 of 59

14 4.6.2 Automatic data input In case of automatic scanning, press the Scan button and the built-in camera of the device switches on allowing us to scan the barcode. Besides reading linear (EAN-8, EAN-13 and GS1-128) bar codes, it can read GS1 QR-code, inverse GS1 QR-code, GS1 Data Matrix, inverse GS1 Data Matrix, GS1 DataBar Omnidirectional (normal, stacked, truncated) and ITF-14. All the ID Keys and AI pairs defined in the General Specification v14 are available to scan, including identification keys and other element sting pairs as well as simple and complex symbols. When scanning symbols, every standard and non-standard symbol is read. The contents of non-standard symbols starting with and www are defined as a website URL and automatically displayed in a new window. If the code contains URL (regardless it is GS1 Standard or not), it will be opened automatically. If the symbol contains more ID keys, then a selection list will be displayed by pressing the Validation button, from which we can select the ID Key you want to check through GEPIR. Release 2.2, Proved, August GS1 AISBL Page 14 of 59

15 Readable types: GS1 DataBar Omnidirectional (stacked, truncated): Scanning several data mediums Stringing If - after scanning a symbol - we wish to scan another one, the application will inquire if we want the new scan to be stringed to the first one (as if they were in the same symbol) or to be overwritten. The rule for symbols that may be stringed together is shown in the table below: First symbol type Appended symbol type New symbol type EAN-8, EAN-13 GS1-128 GS1-128 GS1-128 EAN-8, EAN-13, GS1-128 GS1-128 GS1 DataMatrix GS1 DataMatrix GS1 DataMatrix GS1 QR GS1 QR GS1 QR Release 2.2, Proved, August GS1 AISBL Page 15 of 59

16 4.7 Validation The control functions of Logger version 2.7 work as in the previous versions. While for the display of the results of the validation internet and server access is needed, the qualification function may be run on the device side without any outside connection. Besides the number completed with AI to be checked, the application sends the GPS coordinates of the scanning location in the WGS84/UTM system (if the user has authorised the GPS use in the settings of the mobile phone) and setting values of current GPS ON and GPS OFF given in the settings. Both settings have defaults formed in accordance with former operation principles. In addition to the data of the scanning location, the scanning time, the current time zone (device set) and the unique device ID (s/n) are also transmitted by the application. If the data transmission fails (for example due to the failure of internet connection), the record is stored in the memory of the phone and it is sent at the next data transmission. In case of three failed attempts to send the record, it gets deleted automatically. After successful data transmission the application on the server side can return three types of messages: The number is valid on green background; The number is invalid on red background; The connection is failed on yellow background. In all of the three cases GEPIR return codes (RC) and details of the responding router are displayed on-screen, on the basis of which the status is set. Release 2.2, Proved, August GS1 AISBL Page 16 of 59

17 Clicking on the New log icon (at the bottom of the page) we can initiate a new scan, which starts the validating process again. If the number is invalid, we suggest that you click on the Add Photo button, by which you can take picture(s) of the product on which the GTIN can be found, that you can send to the server. While transferring data, the system sends a report via to the competent MO that should take the necessary next steps. You can also attach picture(s) in the detailed view of the History before reporting it. After sending the report, we cannot attach new picture(s) to the record. The identification of competent MO is done automatically on the basis of the country prefix on the server side. A message is sent to the user upon delivery, including the list of addressees or the description of the failure. Release 2.2, Proved, August GS1 AISBL Page 17 of 59

18 4.7.1 Taking usable pictures is the basis of reports A usable report includes pictures. Pictures should be good enough to provide sufficient information about the brand owner of the product identified with invalid GTINs. Sometimes you may need to take more than one picture. Without pictures about the required information our colleague who receives the report won t be able to follow it up. Reports without pictures are useless for the purpose of GTIN intelligence! How should you do it in practice? As you can see in this example the report includes three pictures: one about the product, one about the barcode with GTIN and another one where you find the contact details of the brand owner. Providing these information the relevant MO could easily follow up the report. Single picture containing all the required information to follow up: Release 2.2, Proved, August GS1 AISBL Page 18 of 59

19 4.7.2 How not to make reports a. Reports about invalid GTINs without picture b. Reports with pictures as follows: a. You can t see the contact details on the product only the barcode b. You can t see the contact details on the product only the barcode c. You can t see the barcode nor the GTIN and contact details 4.8 Qualification The qualification function is based on the GS1Lib program library. GS1Lib - contains the definitions of GS1 General Specifications - checks the rules of its compulsory, excluding and connected pairs, and GS1 prefixes and GS1-8 prefixes. This operating model makes it possible that the GS1 qualification of a scanned symbol or a string recorded manually can be carried out on the mobile client without internet and/or sever connection. The first screen of Qualification is a checklist containing the processed code (scanned or manually recorded) and other parameters of the scanning, the decoded ID Keys, the AI pair checking and the symbol checking. After the successful scanning or the manual data input, the qualification on the device side runs automatically, and the results of the checks appear on the Qualification button in icons of different colours. Green tick means standard, the yellow exclamation mark means correctable (e.g. check digit), or dubious (e.g. unknown use area), and red X means non-standard. Parallel with the Release 2.2, Proved, August GS1 AISBL Page 19 of 59

20 Qualification the Photo button gets activated, and by clicking on it we can attach photo(s) to the record and then send the data to the server side, that checks with the help of the GEPIR system if the identification key such as a company prefix is valid or not. Selecting the decoded elements, you can check the ID Keys one by one or in details by the AI content, min-max length, format, prefix, prefix handler, prefix format, AI support by prefix, separator and substance. By the data content the checklist of the element string pair may show a different number of rows e.g. in the case of faulty or unidentifiable AI s other information isn t displayed, or in the case of other AI s (e.g. date, bulk extent...) we make individual checks (e.g. in case of a date we can check if the month/day data is valid or not), in other case this row doesn t appear at all. 4.9 List of History With the History button we can list the previous checks (records) and the information associated with them. The last ten records are available (default), but users may expand the list with nine new pages of history downloadable one-by-one from the server (a maximum of 100 records). The appearance of the list of history is always preceded by data communication, that is to say all the records are always downloaded from the server. In the list of History the first icon displays the result of the qualification, while the result of the validation (GEPIR query) is shown by the second. Clicking on the given row we can see more information about the record. The detailed data includes the Qualification and the Validation as independent functions on a button respectively, the MO data source belonging to the ID Key. If the number is valid, the name and the address of company prefix owner can be seen (we can even check it on the map due to the Google maps connection of the application), the date when data was sent and Release 2.2, Proved, August GS1 AISBL Page 20 of 59

21 recorded, the pictures attached to the record and the date of report on the record or a function that can provide this possibility in the form of a report button. Furthermore, even in case of unauthorised use, i.e. invalid numbers, the scanning time and the scanning location (along with its GLN, which we can also check on Google maps), the user name and the identifier of the device (GIAI), and the data of GEPIR return codes and responding router are recorded. In case of those records in the location database, which have location data sheets, a URL link will be displayed referring to the data sheet in the scanning location block. Release 2.2, Proved, August GS1 AISBL Page 21 of 59

22 5 Mylogger website The History is also available on a website: On this website every user can sign in with their own login name and password and can list their own records in timeline, and can filter the list, for example by time, location or status. The website is available in eight languages (English, Hungarian, Portuguese, Russian, Czech, German, Latvian and Slovenian). The map of the website briefly: 1. List - The number of records in the History available from the website that can be displayed on one screen 2. My prefix See all of your prefixes 3. Statistics Make statistics from your records based on BQ, Mobile; in different views 4. Batch Query Uploading, validating, sharing huge amount of datas 5. Admin With the right user licence you can admin your datas 6. Contacts Here you can see all of GS1 MO Supervisor s and report handler s name and access Release 2.2, Proved, August GS1 AISBL Page 22 of 59

23 5.1 List The number of records in the History available from the website that can be displayed on one screen is limited, but the number of screens is not. (One may go back even to their first record.) Users cannot delete or modify any record from the history through this webpage either. However, they can modify the display according to their profile settings, and with this they can give others authorisation (e.g. to supervisor) for the exact scanning location of the record or just a limited display of a given area. Users are capable of using dynamic filtering, such as filtering by time period, location, AI s, countries, GS1 ID Keys, scanning devices. Supervisors can use extra filters such as filtering by company, user. Release 2.2, Proved, August GS1 AISBL Page 23 of 59

24 The More details link contains not only the record details, but also a Google map with the exact location of the scan. Release 2.2, Proved, August GS1 AISBL Page 24 of 59

25 As far as the pictures attached to the given records are concerned, you can also see them on the webpage (you can remove and save it at any time) of the record details. Due to the qualification function, the website is suitable for the visualization of the results of both checking methods. The GEPIR status and Logger status columns, standard or non-standard, (according to the GS1 General Specifications) are displayed on the website. In addition, under the GEPIR status, you have the possibility to query the current GEPIR status of the record. Release 2.2, Proved, August GS1 AISBL Page 25 of 59

26 Under the GEPIR and Logger (GenSpec) status, you can see the reasons of invalid numbers and nonstandard numbers. You have an additional possibility under the GEPIR status to query the current GEPIR status of a given number. Release 2.2, Proved, August GS1 AISBL Page 26 of 59

27 At the Time and location of scan block, you can see the exact coordinates of the scan s location. The details tab also contains a Google map with the exact location of the scan and further information with the names and GSRN numbers of the users, the GIAI numbers of the devices and which GS1 MO you/your colleagues belong to. Under the Report status you have the possibility to check if the report has been sent or not, and you can even see more details where you can do further actions. Release 2.2, Proved, August GS1 AISBL Page 27 of 59

28 At report details, you can add your remarks by opening the comments form, getting in touch with the user who scanned the invalid GTIN so you can get more information about the product in an interactive way. About each comment the addressee will get a notification automatically managed by the system. Depending on where the follow up of the given invalid number lasts, you are able to change its statuses too (New, Processing, and Closed). Release 2.2, Proved, August GS1 AISBL Page 28 of 59

29 At the bottom of list view, you have the possibility to download your records from the website in Excel sheet or.csv format. Release 2.2, Proved, August GS1 AISBL Page 29 of 59

30 Release 2.2, Proved, August GS1 AISBL Page 30 of 59

31 5.2 My prefix Users only can see their own ID keys that contain the related MO s prefix. The supervisor and the addressee of the report can see here all the records that contain ID Keys allocated from their MOs prefix (even the barcodes scanned by other users). Release 2.2, Proved, August GS1 AISBL Page 31 of 59

32 5.3 Translation The Translation menu allows you to translate the website and application itself in an interactive way with the help of pictures. 5.4 Statistics After selecting the Statistics menu a Dashboard page will appear. The Statistics Dashboard contains six different types of charts that show statistical data based on records from the current month1. Naturally the period of time can be set on the dashboard. (Please note that the period selected in history view (List menu) has no effect on the Statistics.) 1. Distribution of valid, invalid and faulted records 2. Distribution of standard and nonstandard records 3. Distribution of data content (AI combinations) 4. Distribution of symbol types 5. Distribution of GEPIR return codes - only available for GS1 MO Supervisors 6. Distribution of GS1Lib return codes - only available for GS1 MO Supervisors 1 e.g. opening the Statistics dashboard page on the statistical data for the period of is shown Release 2.2, Proved, August GS1 AISBL Page 32 of 59

33 Click on the [Details] button to go to the sub-page of the chosen statistics and to get more detailed statistical information. On sub-pages the data is shown according to the time period previously set on the dashboard. Release 2.2, Proved, August GS1 AISBL Page 33 of 59

34 5.4.1 Statistics sub-pages Distribution of valid, invalid and faulted records The bar chart on the left shows the distribution of scanned records divided into the three GEPIR statuses (valid, invalid and faulted) per MOs. If the cursor is moved over an MO on the diagram, the number of records will be displayed. The pie chart shows the number of scanned records by GEPIR statuses (valid, invalid and faulted). The pie chart provide drill-down functionality: detailed statistical data can be queried for each status by clicking on a slice of the chart: Level 1. Distribution of records between MOs that initiated the queries Level 2. Distribution of records between the users of the selected MO Level 3. Distribution of records of the selected user between MOs who allocated the requested ID Keys The current level is shown below the name of the chart. Release 2.2, Proved, August GS1 AISBL Page 34 of 59

35 Invalid The table under the diagrams shows the exact values for the percentages displayed in the pie chart. Both mobile and batch query records can be included in this statistics. The time span can be modified at the top of the page. Release 2.2, Proved, August GS1 AISBL Page 35 of 59

36 Logging in as a GS1 MO Supervisor you can filter by company name, therefore creating statistics related to a specific company. The charts can be exported into image file. The statistical data can be exported into excel sheet or.csv file. Release 2.2, Proved, August GS1 AISBL Page 36 of 59

37 Distribution of standard and nonstandard records The bar chart on the left shows the distribution of scanned records divided into GS1Lib statuses (standard and nonstandard) per MOs. If the cursor is moved over an MO on the diagram, the numbers assigned to it will be displayed. The pie chart on the right shows the number of scanned records by GS1Lib status. The pie chart provide drill-down functionality: detailed statistical data can be queried for each status by clicking on a slice of the chart: Level 1. Distribution of records between MOs that initiated the queries Level 2. Distribution of records between the users of the selected MO Below the name of the chart the current level is shown. The table under the diagrams shows the exact values for the percentages displayed in the pie chart. Release 2.2, Proved, August GS1 AISBL Page 37 of 59

38 Nonstandard The time span can be modified at the top of the page. Release 2.2, Proved, August GS1 AISBL Page 38 of 59

39 Logging in as a GS1 MO Supervisor you can filter by company name, therefore creating statistics related to a specific company. The charts can be exported into image file. The statistical data can be exported into excel sheet or csv file. Release 2.2, Proved, August GS1 AISBL Page 39 of 59

40 Distribution of data content (AI combinations) Distribution of symbol types Release 2.2, Proved, August GS1 AISBL Page 40 of 59

41 Distribution of GEPIR Return Codes This type of statistics is available only for GS1 MO Supervisors. Release 2.2, Proved, August GS1 AISBL Page 41 of 59

42 The pie chart shows the distribution of GEPIR Return Codes. Detailed statistical data can be queried for each Return Code by clicking on a slice of the chart: Level 1. Distribution of records between MOs that responded the selected RC The current level is shown below the name of the chart. R C 9 9 The table under the diagram shows the exact values for the percentages displayed in the pie chart. The statistical data can be exported into excel sheet or csv file. Both mobile and batch query records can be included in this statistics. The time span can be modified at the top of the page. Release 2.2, Proved, August GS1 AISBL Page 42 of 59

43 The charts can be exported into image file. Release 2.2, Proved, August GS1 AISBL Page 43 of 59

44 Distribution of GS1Lib Return Codes This type of statistics is available only for GS1 MO Supervisors. The pie chart shows the distribution of GS1Lib return codes. Detailed statistical data can be queried for each GS1Lib Return Code by clicking on a slice of the chart: Level 1. Distribution of records between MOs that received the selected return code for their queries Below the name of the chart the current level is shown. Release 2.2, Proved, August GS1 AISBL Page 44 of 59

45 I N V A L I D A I The table under the diagram shows the exact values for the percentages displayed in the pie chart. The statistical data can be exported into excel sheet or csv file. Release 2.2, Proved, August GS1 AISBL Page 45 of 59

46 The time span can be modified at the top of the page. The charts can be exported into image file. Release 2.2, Proved, August GS1 AISBL Page 46 of 59

47 5.5 How to use the Admin website The Admin website can be accessed by GS1 MO and Company Supervisors on the following URL: As a GS1 MO Supervisor you will see the list of the companies linked to your MO Activate a new company registration When a new company is being registered in the system, the GS1 MO Supervisor receives a notification about the registration. The company and supervisor data is saved in the system, but they are inactivated. You can activate a new company by taking the following steps: 1. Click on the direct URL included in the notification it will open the Admin website 2. On the Admin website you will get to the Company Supervisor s datasheet 3. Check the [Active] checkbox at the bottom of the page 4. Click on [Save] 5. Send an to the Company Supervisor about the successful registration Release 2.2, Proved, August GS1 AISBL Page 47 of 59

48 5.5.2 Edit company data If for some reason the information related to a company should be changed, you can do that on the company datasheet. Go to the Admin website and click on the Edit button on the row of the company whose data you want to change. On the company datasheet you will see the name, address, verification code and country of the company. If you want to withdraw the Logger access from a company, you have to deactivate all the users of that company (see next chapter) Edit users data If you want to see the list of your MO s users just click on the [Users] link at the top of the page. If you need the list of users of a specific company, click on the [Users] link on the row of the given company. Release 2.2, Proved, August GS1 AISBL Page 48 of 59

49 On the user list click on the Edit button on the row of the user whose data you want to change. On the user datasheet you can see/change the username, address and role of the user, and you can activate/deactivate the user. Release 2.2, Proved, August GS1 AISBL Page 49 of 59

50 5.6 Batch query After logging in on the website the Batch query function can be found on the top of the page in the Menu. The list of ID Keys can be uploaded on the Batch query page. Press the [Browse] button then select the Excel file which contains the ID Keys to be checked. File format: Please upload an Excel file with.xlsx extension (Excel spreadsheet created with Office 2007 or newer). Please note that the.xls format is not supported! File content: The uploaded Excel file must contain only one spreadsheet. The number of columns in the Excel uploaded is limited: GS1 ID Key + max. 4 columns. The number of rows is limited: in one column can be uploaded rows in case of uploading more columns is If you have a list that contains the requested ID Keys, but not the GLN of the company which uses that ID Key you can upload a spreadsheet in the following format: The first column (column A) contains the name of the GS1 ID Key (e.g. GTIN, GLN, SSCC, GRAI etc.). This column must contain only one type of ID Key (specified in the first row). The following columns (2-4) can contain additional data relating to the GS1 ID key (manufacturer, product name etc). These data can also be seen in the outcome Excel, helping the processing. If you have a list that contains not only the requested ID Keys (e.g. GTINs) but also the GLN of the company which uses that ID Key, then you can upload a spreadsheet in the following format: Column A: in the header (1st row) the name of the GS1 ID Key (e.g. GTIN, GLN, SSCC, GRAI etc.), underneath the ID Keys (one key per cell). The column must contain only one type of ID Key (specified in the first row). Column B: in the header (1st row): GLN, underneath the GLNs associated to the ID Key in the Column A (one GLN per cell). The following columns (2-4) can contain additional data relating to the GS1 ID key (manufacturer, product name etc). These data can also be seen in the outcome Excel, helping the processing. Release 2.2, Proved, August GS1 AISBL Page 50 of 59

51 The selected file can be renamed. Fill in the field of Company name with the name of the company that provided the list (optional). After uploading the file (press [Upload] button), the system checks the file and data content format. As a result, the following information is shown on the page: Total number of lines in the uploaded file Number of ID Keys that are not in line with the GS1 Standards (e.g. invalid check digit, length or character set) Press [Download] to download the list of ID Keys with the result of format checking (the nonstandard ID Keys are marked in the originally uploaded file). Press [Run] to start the query through GEPIR. A progress bar shows the percentage of the processed ID Keys. The process continues on the server, therefore you can close the browser and turn back to this page later on. Release 2.2, Proved, August GS1 AISBL Page 51 of 59

52 When the query is finished, the result is shown in a table and the whole data set (the list of uploaded ID Keys with statuses, party information etc.) can be exported into Excel spreadsheet. Furthermore, if there are invalid numbers, by pressing the [Send report] button you can send a notification to the competent MO(s) to take the necessary next steps. After clicking on this button once, it becomes inactive showing that the report has already been sent. If there aren t any invalid numbers found during the checking, the [Send report] button is inactive. Pressing the [Send report] button a Comment window will appear. Add a remark to the notification e- mail in order to help the receiver with the follow-up of reported numbers. Release 2.2, Proved, August GS1 AISBL Page 52 of 59

53 Release 2.2, Proved, August GS1 AISBL Page 53 of 59

54 Content of the notification Below you will see the that is sent by the system to the relevant GS1 MO. The report handler will get the link to the list of reported invalid ID Keys. Subject: Logger for Staff Report invalid ID Keys Dear GS1 Logger Staff Report Administrator, This is an automatically generated notification . Please do not reply to this . A list of GS1 ID Keys has been uploaded to Logger for Staff platform. After checking this list through GEPIR, the batch query service indicated that the GEPIR status of the following GS1 ID Keys are invalid. Please see the invalid keys belonging to your country on the following link: <direct link to the list of reported Id Keys Excel spreadsheet format> You received this list of GS1 ID Keys since the GCPs belong to your country. The list was uploaded by <user name> from <GS1 MO> using the following address: < address>. Uploader s comment: < - > Even if the list of ID Keys may not be enough to explore and identify the reason of their invalid status but you may contact the relevant GS1 MO or company who uploaded the original list and initiated the batch query. Should you need further information about GS1 Logger or need assistance, please contact the GS1 Logger Support at lfs_support@gs1hu.org. Kind regards, GS1 Logger Team Release 2.2, Proved, August GS1 AISBL Page 54 of 59

55 5.6.1 How to use BQ webservice In order to use the Batch Query function of LFS system, you can upload/download Excel file of GS1 Identification (ID) keys via mylogger website or you can use Batch Query Web Service (2) to upload ID keys. This section describes the latter solution. Service Characteristics Fig. 1 shows the whole process of a GS1 ID key upload and it also presents the web service operations (actions) related to the main phases of general data uploading and processing within Batch Query. To apply Batch Query web service, client partner should develop a web service client application based on the WSDL file (3) of Batch Query web service. The web service client should implement seven operations: 1. GetQueryGroups to get previously uploaded data (groups). 2. GetSessions to get sessions related to a group. 3. ValidateQueryGroup to validate uploaded data based on GS1 Lib data source. 4. RunQueryGroup to upload and run query related to uploaded data in the Batch Query database based on information of GEPIR data source. 5. RunExistingQueryGroup to run query based on an existing group ID. 6. GetSessionProgress to get information about the state of processing session. 7. GetSessionResult to get information about the final state of processing session. Fig. 1. Batch Query process and related web service operations 2 The Batch Query Web Service applies SOAP-based messaging technology. 3 The WSDL file is available here: Release 2.2, Proved, August GS1 AISBL Page 55 of 59

56 Details of Batch Query Web Service The seven mentioned operations of Batch Query web service should be implemented by the following way. Notes: The exact description of Batch Query web service is included in the WSDL file of service. To use operations, the valid authentication data (username/password) is the general preliminary input parameter. 1. GetQueryGroups: This operation is to get information about previously uploaded groups (lists of ID Keys). A list can be run more times without re-uploading data group and it can be run after a finished session as well. This operation returns: a. Company name b. Group ID c. Type of ID key including in the group d. Information about last session(s) if it already run e. other group data (see WSDL) 2. GetSessions: This operation is to get information about every session related to a data group. The input parameter is a group ID. This operation returns a. ID of a session b. Starting date/finish date of a session c. Count of valid/invalid GLN d. Count of valid/invalid ID key e. other session data (see WSDL) 3. ValidateQueryGroup: This operation is to get result about ID key format validation based on GS1 Lib data source. The input parameters are the ID key type as well as ID keys and optionally the GLN numbers related to each ID Key. This operation returns an OK or a format error type (e.g. CDVError ). 4. RunQueryGroup: This operation is to upload an ID Key list and run query in Batch Query database based on information GEPIR data source. The input parameters are a. Name of run b. Company name c. ID key type d. ID key with GLN number e. This operation returns a session ID. 5. RunExistingQueryGroup: This operation is similar to RunQueryGroup operation but the input parameter is only the group ID of a previously uploaded Query Group in this operation. The operation returns session ID as well. Release 2.2, Proved, August GS1 AISBL Page 56 of 59

57 6. GetSessionProgress: This operation is to get information about the state of a running session. The input parameter is a session ID as well as page number of session. Therefore you can query only a part of processed data. This operation returns the state of running session in percentage. 7. GetSessionResult: This operation is to get information about completed session. The input parameters are the same as in case of GetSessionProgress operation. This operation returns a. ID key b. ID key status (valid, invalid, faulted) c. GEPIR-based responses: return code related to an ID key, response key related to an ID key, GLN-specific response key related to an ID key d. GLN number History of queries All the uploaded files (both via website and web service) and query results are stored on the server, therefore each user can see the history of queries previously initiated. Release 2.2, Proved, August GS1 AISBL Page 57 of 59

58 Queries can be initiated for an uploaded file any time without re-uploading the list by pressing the [Run] button beside the file name. All the results related to the same file are listed under the filename. Click on the icon to see all the queries related to the selected file. Release 2.2, Proved, August GS1 AISBL Page 58 of 59

59 5.7 Contacts GS1 Logger User Manual Guide If you have further questions, on this page you will find the username and address of the registered MO s report handler and supervisor. Enjoy the new features. Should you need further information about GS1 Logger or need assistance, please contact the GS1 Logger support at lfs_support@gs1hu.org. Kind regards, GS1 Logger Team Release 2.2, Proved, August GS1 AISBL Page 59 of 59