Prior considerations
The user must open the native application to be able to establish the connection between the scanning device and the CÒPIA service web application ( more information )
Note: Given the complexity of configuring network scanners, we recommend using local scanners.
Step 1: Select a template or no template
To generate the copy, simply click the “Create a copy” button.
Then, a pop-up appears that allows you to choose whether to generate the copy using a template (this option allows the user not to have to fill in most of the configuration fields because they are already informed) or without a template (implies that the user will have to fill in all the fields)
Step 2: Fill in or review the configuration and metadata fields:
Depending on what has been chosen (template or without), the user must fill in the mandatory fields (and, optional, if applicable) that appear highlighted in red:
- body issuing the copy
- Original document support:
- Paper: in case you want to make an authentic copy of a paper document using a scanner
- Electronic: in case you want to make an authentic copy of an electronic document (in this case, only copies of documents in PDF format are allowed)
- Copy title
- Identifier of the original document
The fields to be filled in are grouped into three blocks:
- Copy configuration settings
- Copy metadata
- Registry metadata: a completely optional block designed for users who want to make a copy of a document presented in the entity's entry and exit registry. The tool allows you to include a stamp with the registry data in the copy or, if you do not want it, it will be included as metadata.
Step 3: Generating the copy
Once all the fields have been filled in, simply click on the “Generate” button.
Then, a screen opens with the web component to make the copy:
- In case of generating a copy of a paper document click here
- If you want to generate a copy of an electronic document, click here.
- If you want to generate a copy that includes the entry and exit stamp, click here.
More information about metadata and configuration fields:
| Name | Description | Example |
| Body issuing the copy | Standardized identifier of the body that has been assigned the competence to issue authentic copies | Secretariat or code DIR3 |
| Original document support | Indicates the nature or medium of the original document from which a copy will be made | Paper |
| Secure verification code on copy | The CSV is a unique reference that is given to each document, made up of a set of characters and generated electronically. This reference allows the document to be identified, linked to its issuer and its authenticity and integrity to be verified through access to the electronic office. |
Yes |
| Copy verification URL via CSV | URL, available in the entity's Electronic Office, which allows you to check the authenticity and integrity of the authentic paper copies of electronic administrative documents issued by the entity.
Important: If you want the CSV to also appear in the URL, you must enter the URL as follows: url + {0}. For example: http://csv.domini.cat/csv?id={0} NOTE: If your organization does not have its own CSV verification page, you do not need to report this field or any that refers to the CSV. The Copy service does not have a secure verification code verification page. |
If you want to include the CSV in the URL: http://csv.domini.cat/csv?id={0} If you do not want to include the CSV in the URL: http://csv.domini.cat/ |
| CSV generation mechanism | Indicates the way in which the CSV will be generated. If automatic is selected, the service itself will generate the code following the following pattern: [INE code of the entity][DDMMYYYY][RANDOM_FACTOR]. If manual is selected, the user must inform it when generating the copy. | Automatic |
| Reference to the order that regulates the CSV system | Reference to the order, resolution or document that regulates the entity's CSV generation system | |
| Copy signature | Indicates whether the authentic copy must be signed or not. | Yes |
| Signature mechanism | The mechanism that will be used to sign the authentic copy is either the “Signador centralitzat of the AOC Consortium” which holds the entity's electronic seal or the “Local digital certificate” which allows the use of a digital certificate stored on the user's local cryptographic device. | Signador centralitzat of the AOC Consortium |
| Signature visible on copy | Indicates whether the electronic signature of the authentic copy should be visible or not in the resulting document. | Yes |
| Copy title | Title or name of the true copy | Copy of writing XXX |
| Copy subject | Brief summary of the topic/subject of the copy | |
| Identifier of the original document | the identifier of the source document from which the copy will be made | 010203 |
| Document author | Name or identifying data of the author of the source document | Peter Poma |
| Document origin | Indicates whether the content of the source document was created by the citizen or by an Administration | Citizen |
| Access regime | Regime of access to the authentic copy. To choose from a list of values | Free access |
| Production status | Indicates the nature of the copy. Values to choose from a list. It is important that the value indicated matches the support of the original document. | Authentic electronic copy of paper document |
| Metadata visible in the copy | Indicates whether the minimum metadata should be printed and visible on the authentic copy. If so, the content of the original document will be scaled to 80% of its original area and the metadata will be printed in the resulting margin. | Yes |
| Document type |
Document type of the document to choose from a list | Minutes |
| Copy expiration date |
Date on which the validity of the authentic copy will expire. The date format must be dd:mm:yyyy hh:mm:ss. | 12/04/2025 13:48:29 |
| Nature of the source document | Indicates the nature of the source document from which the copy will be made. The values to choose are: original, authentic copy and copy | Original |
| Date of original document |
Date the original document was created. The date format must be dd:mm:yyyy hh:mm:ss | 12/04/2018 13:48:29 |
| Language |
Define the language of the document. According to the e-EMGDE, this metadata must report two parameters:
In both cases it will be an Alpha-2 code, that is, a two-letter code for the country and for the language. |
es_ES, ca_ES, gl_ES, eu_ES (Spanish, Catalan, Galician, Basque) |
| Visible seal | Allows you to visibly include a stamp with the entry/exit registration data on the copy | Yes |
| Check-out number |
Output record number associated with the source document | S/000016-2018 |
| Check-out date | Date of the output record associated with the source document. The date format must be dd:mm:yyyy hh:mm:ss | 12/04/2018 13:48:29 |
| Check-in number | Entry record number associated with the source document | E/000016-2018 |
| Check-in date |
Date of the entry associated with the source document. The date format must be dd:mm:yyyy hh:mm:ss | 11/04/2018 13:48:29 |