Last modified by caterina on 2021/10/27 16:31
From version 9.1
edited by caterina
on 2021/10/27 17:31
Change comment: There is no comment for this version
To version 3.1
edited by melanie@one-count_com
on 2016/12/06 15:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Import - How to Import a File
1 +Import - How to Import a File (v12.x)
Parent
... ... @@ -1,1 +1,0 @@
1 -User Operations - Managing Your Data
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.caterina
1 +XWiki.melanie@one-count_com
Content
... ... @@ -1,35 +4,28 @@
1 -{{layout}}
2 -{{layout-section ac:type="two_right_sidebar"}}
3 -{{layout-cell}}
4 4  
5 5  
6 6  {{id name="Start ScreenSteps Content"/}}
7 -This lesson will describe how to use the Import Engine to upload a CSV formatted list of users into the ONEcount database.
4 + This lesson will describe how to use the Import Engine to upload a CSV formatted list of users into the ONEcount database.
8 8  
9 9  Please refer to Quick Start Guide - User Operations for important information about basic concepts and rules relating to imports and bulk operations.
10 10  
11 -=== OPEN THE "IMPORT" WINDOW ===
8 +=== OPENING THE "IMPORT" WINDOW ===
12 12  
13 -**Select USER OPERATIONS from the Main Menu.**
10 +=== Select USER OPERATIONS from the Main Menu. ===
14 14  
15 -[[image:attach:Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 3.png||thumbnail="true" height="250"]]
12 +[[image:attach:media_1443213231223.png||align="center"]]
16 16  
17 -**Click on "IMPORT" in the sub-menu.**
14 +=== Click on "IMPORT" in the sub-menu. ===
18 18  
19 -\\
16 +[[image:attach:media_1443213261172.png||align="center"]]
20 20  
21 -[[image:attach:Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 4.png||thumbnail="true" height="250"]]
18 +=== The "Import" window will open, where you begin begin the import process. ===
22 22  
23 -**The "Import" window will open, where you begin begin the import process.**
24 -
25 25  [[image:attach:media_1443213294962.png||align="center"]]
26 26  
27 27  === IMPORT STEPS ===
28 28  
29 -==== Select Import File ====
24 +=== 1. In the Import window choose your import file using the "Browse" button (1), and select "Upload File" (2). ===
30 30  
31 -**~1. In the Import window choose your import file using the "Browse" button (1), and select "Upload File" (2).**
32 -
33 33  [[image:attach:media_1443213396710.png||align="center"]]
34 34  
35 35  The list will be uploaded, and the Import window opened. You will see a confirmation that the list was uploaded successfully, along with the number of records uploaded. (See screen shot below.) //**The list has not been imported at this point but uploaded to the system in preparation for import.**//
... ... @@ -36,12 +36,8 @@
36 36  
37 37  [[image:attach:media_1406494045151.png||align="center"]]
38 38  
39 -\\
32 +=== 2. Give your import an Import Title (1), Import Description (2), select a Source Code (3), select the product term(s) from the Product List (4), and select a Product Status. ===
40 40  
41 -==== Complete Import Information ====
42 -
43 -**2. Give your import an Import Title (1), Import Description (2), select a Source Code (3), select the product term(s) from the Product List (4), and select a Product Status.**
44 -
45 45  [[image:attach:media_1443549296560.png||align="center"]]
46 46  
47 47  Note that the product terms are what appear in the list of products (#4 above) in the Import Engine. Because all products have a term(s) and if a product has multiple terms (i.e. a free print subscription and a paid print subscription), each term needs to appear in the "product" list so that a user can be subscribed to that specific term.
... ... @@ -49,7 +49,7 @@
49 49  **Source Codes** are used to track the source of a transaction, ie the source of the user/name in the ONEcount database.* When assigned to a form, a source code can be used as a selection when generating lists and reports, to track what form a user/subscriber completed, to track what list a user came from when importing users, or to show which e-mail campaign a user came from . (A source code tag can be appended to links in a newsletter campaign to override a source code assigned when a form is created, which allows you to identify that a user was directed to a form and came into the system from a link in that campaign.) Source Codes are created using the Source Codes tool in the INVENTORY module.
50 50  
51 51  *For audited publications, source codes that identify the source of user names in accordance with cagetories in Paragraph 3b reports should be created. Forms and imported lists should be assigned the appropriate source code for the source of the name. For example:
52 -1) You want to identify all Internet Direct Requests from a subscription form, so you would create a source code called, for example, IDRPrintForm and attach it to the subscription form. This source code will be attached to any user record created when a user subscribes using that form. The source codes indicates it was an Internet Direct Request from the form, and when a 3b report is generated those users will be included in the count for internet direct requests.
41 + 1) You want to identify all Internet Direct Requests from a subscription form, so you would create a source code called, for example, IDRPrintForm and attach it to the subscription form. This source code will be attached to any user record created when a user subscribes using that form. The source codes indicates it was an Internet Direct Request from the form, and when a 3b report is generated those users will be included in the count for internet direct requests.
53 53  2) You want to identify all Telecommunications Direct Requests from a telemarketing renewal campaign, so you create source code called, for example, TDR05152104 to identify that renewal list imported on May 15, 2014. When doing the import to update/renew, select that source code and all records imported will have that source attached to their record in ONEcount. So, when generating a 3b report those renewed users will be included in the count for telecommunications direct requests.
54 54  
55 55  If you have a master file including multiple codes for circulationc sources, separate the file by source (e.g. a sub-file for each 3b category/source of circulation) and import each sub-file using the appropriate source code created in ONEcount.
... ... @@ -58,12 +58,8 @@
58 58  
59 59  Below the Product List, you will see a list of any existing Import Mappings (templates), if any.
60 60  
61 -\\
50 +=== 3a. If using an Import Mapping Template: Below the Product List, you will see a list of any existing Import Mappings (templates). Find the template you wish to use and select "Use" then proceed to Step 5.. ===
62 62  
63 -==== Map Data ====
64 -
65 -**3a. If using an Import Mapping Template: Below the Product List, you will see a list of any existing Import Mappings (templates). Find the template you wish to use and select "Use" then proceed to Step 5.**
66 -
67 67  [[image:attach:media_1362667166234.png||align="center"]]
68 68  
69 69  For information on how to use and/or create mapping templates, see the lessons "How to Use an Import Mapping Template" and "How to Create an Import Mapping Template".
... ... @@ -70,16 +70,12 @@
70 70  
71 71  You may select to use a template and then modify it by adding/removing fields to be mapped (as described in Step 4.)
72 72  
73 -\\
58 +=== 3b. If not using an Import Mapping Template: The mapping function is found below the list of mapping templates. Proceed to Step 4. ===
74 74  
75 -**3b. If not using an Import Mapping Template: The mapping function is found below the list of mapping templates. Proceed to Step 4.**
76 -
77 77  [[image:attach:3b.__If_not_using_an_Import_Mapping_Template__The_mapping.png||align="center"]]
78 78  
79 -\\
62 +=== 4. Proceed to the mapping section and map your fields (either from scratch or by modifying an Import Mapping Template). ===
80 80  
81 -**4. Proceed to the mapping section and map your fields (either from scratch or by modifying an Import Mapping Template).**
82 -
83 83  [[image:attach:4._Proceed_to_the_mapping_section_and_map_your_fields___1.png||align="center"]]
84 84  
85 85  (% style="text-decoration: underline;" %)**Definitions**(%%)**:**
... ... @@ -105,12 +105,8 @@
105 105  
106 106  Question Header and CSV Header field names don't need to be identical, e.g. a Question Header may be "Email Address" and CSV Header "Email".
107 107  
108 -\\
89 +=== 5. DO NOT SKIP THIS STEP – ALWAYS CHECK FOR DUPLICATES! Check the box for the Active Question Header(s) you want to check for duplicates against. ===
109 109  
110 -{{error}}
111 -**5. DO NOT SKIP THIS STEP – ALWAYS CHECK FOR DUPLICATES! Check the box for the Active Question Header(s) you want to check for duplicates against.**
112 -{{/error}}
113 -
114 114  [[image:attach:5.__DO_NOT_SKIP_THIS_STEP_--_ALWAYS_CHECK_FOR_DUPLICATES_.png||align="center"]]
115 115  
116 116  In the screen shot above, the system will check for duplicates against the Email and Last Name fields. A duplicate would be identified when a record being imported has the same email address AND last name as a record already in the ONEcount database.
... ... @@ -117,115 +117,64 @@
117 117  
118 118  You can select multiple headers to check for duplicates, but be aware that ONEcount uses “AND” logic when doing so. (% style="color: rgb(0,0,0);" %)For example, if you select to check email, first name, and last name fields for duplicates, ONEcount will look for records in the ONEcount database that have the same email AND first name AND last name as a record being imported. A record would be a duplicate only if all three fields match.
119 119  
120 -\\
97 +(% style="color: rgb(255,0,0);" %)**When checking for duplicates, ONEcount is not checking for duplicates within the import file but only between the ONEcount database and the file being imported. If your import file contains duplicates within it and no matching records are found in ONEcount, the duplicate records in the import file will be imported.**
121 121  
122 -{{error}}
123 -It is important to be sure that records in ONEcount and the import file contain data for the fields you are checking for duplicates against. If they don't, a record may not be matched as a duplicate. For example, you check for duplicates against email AND last name: a record in ONEcount has the same email as a record in the import file and the ONEcount record DOES include last name. The record in the import file DOESN'T include last name. The record won't be counted as a duplicate because the email AND last name do not match.
124 -{{/error}}
99 +(% style="color: rgb(255,0,0);" %)**It is important to be sure that records in ONEcount and the import file contain data for the fields you are checking for duplicates against. If they don't, a record may not be matched as a duplicate. For example, you check for duplicates against email AND last name: a record in ONEcount has the same email as a record in the import file and the ONEcount record DOES include last name. The record in the import file DOESN'T include last name. The record won't be counted as a duplicate because the email AND last name do not match.**
125 125  
126 -**
127 -**
128 -
129 -{{tip}}
130 -When checking for duplicates, ONEcount is not checking for duplicates within the import file but only between the ONEcount database and the file being imported. If your import file contains duplicates within it and no matching records are found in ONEcount, the duplicate records in the import file will be imported.
131 -{{/tip}}
132 -
133 -{{tip}}
134 134  If importing a new list and email is a required field for all records (e.g. for an e-newsletter-type product), it is recommended to check for duplicates across ***email**.* _ (% style="color: rgb(255,0,0);" %)**Note that if a user has a different email in the import list than in ONEcount and you check only by email, the record won't be identified as a duplicate**(%%)_(% style="color: rgb(255,0,0);" %). (%%)If the emails match (and the records identified as duplicates) and you wish to append data to that record and/or subscribe to a new product via the import file, you will need to select to process duplicates after new records are imported. This will process ALL duplicates.
135 -{{/tip}}
136 136  
137 -{{tip}}
138 -If you are re-importing a list that was exported from ONEcount, e.g. to change data in a demographic field for multiple records, the best field to check against is "User Account Number" (ONEcount ID or ocid) because each user can have only one OCID. (% style="color: rgb(255,0,0);" %)//** Note that at the current time, you can't name a column in your import file "ocid". If you do, the system will give you an error message telling you to use a variation such as "oc_id". So, if you have a column with ocid's in your import file, title it "oc_id" and map it to "User Account Number" to dedupe against ocid.**//
103 +If you are re-importing a list that was exported from ONEcount, e.g. to change data in a demographic field for multiple records, the best field to check against is "User Account Number" (ONEcount ID or ocid) because each user can have only one OCID. (% style="color: rgb(255,0,0);" %)//**Note that at the current time, you can't name a column in your import file "ocid". If you do, the system will give you an error message telling you to use a variation such as "oc_id". So, if you have a column with ocid's in your import file, title it "oc_id" and map it to "User Account Number" to dedupe against ocid.**//
139 139  
140 -//For example~:// You wish to change an assigned code (e.g. a class or subscription type code) for a group of users subscribed to a particular product. First, you would export the list (for more on how to generate lists see the LISTS AND REPORTS Manual), then do a "find and replace" for the code in the exported csv file, and then reimport the file with the new code. The Bulk Operations feature allows you to make bulk status changes, product changes, unsubscribes/ kills, subscriptions to additional products, and to delete multiple records without having to reimport a list. It does not allow for bulk demographic changes at this time. More information can be found in the [[BULK OPERATIONS >>doc:Import and Bulk Operations Essentials]]section of the USER OPERATIONS Manual.
105 +//For example~:// You wish to change an assigned code (e.g. a class or subscription type code) for a group of users subscribed to a particular product. First, you would export the list (for more on how to generate lists see the LISTS AND REPORTS Manual), then do a "find and replace" for the code in the exported csv file, and then reimport the file with the new code. The Bulk Operations feature allows you to make bulk status changes, product changes, unsubscribes/ kills, subscriptions to additional products, and to delete multiple records without having to reimport a list. It does not allow for bulk demographic changes at this time. More informaiton can be found in the BULK OPERATIONS section of the USER OPERATIONS Manual.
141 141  
142 -\\
143 -{{/tip}}
107 +=== 6. Select from the Request Date drop-down menu the field/column from your import file to map as the Request Date. (If you don't map this field, the Request Date will be the same as the Transaction Date, which is the date of the import.) ===
144 144  
145 -\\
146 -
147 -==== Request Date | Expiration Date | Link to Media Files ====
148 -
149 -**6. Select from the Request Date drop-down menu the field/column from your import file to map as the Request Date. (If you don't map this field, the Request Date will be the same as the Transaction Date, which is the date of the import.)**
150 -
151 151  [[image:attach:6.__Select_from_the_Request_Date_drop-down_menu_the_fie_1.png||align="center"]]
152 152  
153 -{{tip}}
154 154  Setting a request date ensures that when processing duplicates only data in the ONEcount database that is older than data in the import file will be written over. ONEcount will compare the request date to the date of the most recent information in the database and only write over information that is older than the request date. //This is done on a field-by-field basis within a record.//
155 -{{/tip}}
156 156  
157 157  **For example**:
158 158  
159 -(% style="margin-left: 30.0px;" %)
160 160  A list is being imported on 01/07/2013, and an import record is identified as a duplicate.
161 161  
162 -(% style="margin-left: 30.0px;" %)
163 163  The mapped request date of the import record is 12/01/2012, and the user's last name in the import file is Smith.
164 164  
165 -(% style="margin-left: 30.0px;" %)
166 166  The user updated her profile in the ONEcount database by changing her last name from Smith to Jones on 12/31/2012.
167 167  
168 -*
169 -** When duplicates are processed, her last name WILL NOT be written over, as she changed it AFTER (12/31/2012) the request date of the import record (12/01/2012).
121 +* When duplicates are processed, her last name WILL NOT be written over, as she changed it AFTER (12/31/2012) the request date of the import record (12/01/2012).
170 170  
171 -(% style="margin-left: 30.0px;" %)
172 172  As of 11/25/2012 her job title in the ONEcount database is "Sales Associate".
173 173  
174 -(% style="margin-left: 30.0px;" %)
175 175  In the import record (Request Date 12/01/2012), her job title is "Regional Sales Manager".
176 176  
177 -(% style="margin-left: 30.0px;" %)
178 178  When duplicates are processed, her job title WILL be written over, as the data as of the request date (12/01/2012) is more recent than the data in the ONEcount database (11/25/20120.
179 179  
180 -(% style="margin-left: 30.0px;" %)
181 181  If no request date is set when importing, the request date will be the date of the import. If this were the case in the example above, both the user's last name and job title would be written over as the request date (01/07/2013, which is the date of the import/transaction) would be more recent than the dates in the ONEcount database.
182 182  
183 -(% style="margin-left: 30.0px;" %)
184 184  If there is a blank field in an import file and the corresponding field in the ONEcount database contains data, that field in the ONEcount database will NOT be written over with a blank, even if the Request Date of the import is more recent than the date the information was entered into the ONEcount database.
185 185  
186 -(% style="margin-left: 30.0px;" %)
187 187  If "Null" is inserted into a field in the import file and the corresponding field in the ONEcount database contains data, that field in the ONEcount database WILL BE written over with a blank if the request date of the import is more recent than the date the information was entered into the ONEcount database. If the request date is older than the date the information was entered in the database, the corresponding field will NOT be written over with a blank.
188 188  
189 -(% style="margin-left: 30.0px;" %)
190 -\\
135 +=== 7. Select the column/field in your import file to specify the product Expiration Date. (If you don't specify this, the product Expiration Date will be based upon the Transaction Date, which is the date of the import.) ===
191 191  
192 -**7. Select the column/field in your import file to specify the product Expiration Date. (If you don't specify this, the product Expiration Date will be based upon the Transaction Date, which is the date of the import.)**
193 -
194 194  [[image:attach:7.__Select_the_columnfield_in_your_import_file_to_specify.png||align="center"]]
195 195  
196 196  The expiration date is automatically calculated when a user subscribes online based on the transaction date (which is the date of the online subscription). If a subscription transaction with an expiration date is recorded in the system via an import – especially for data conversions when implementing a new ONEcount system – "Expiration Date" (or something similar) should be a field in the CSV import file. If you do not select this field to be recorded as the expiration date in the ONEcount system, the system will set the expiration date based on the transaction date (which isn't an issue for new subscribers being imported into the system.)
197 197  
198 -(% style="margin-left: 30.0px;" %)
199 199  **For example:**
200 -A product has a term of three years.
142 + A product has a term of three years.
201 201  If a user subscribes online, their subscription will expire three yeasr from the date of their submittal of the subscription form.
202 202  If, however – as in the case of an initial data conversion when implementing a new ONEcount system – lists of users who didn't subscribe to the products online via the ONEcount system are being imported, the import files should contain a field with the expiration date based on the actual subscription date, and that field should be selected as the expiration date. Otherwise, the system will look at the date of import (transaction date) and set the expiration date as three-years from then.
203 203  
204 -\\
146 +(% style="color: rgb(255,0,0);" %)**Note that if you select Expiration Date and select multiple products when importing, the value of that field for each row of the import file will be used to update the Expiration Date for //all// of the products selected.**
205 205  
206 -{{error}}
207 -Note that if you select Expiration Date and select multiple products when importing, the value of that field for each row of the import file will be used to update the Expiration Date for //all// of the products selected.
208 -{{/error}}
209 -
210 -**
211 -**
212 -
213 -\\
214 -
215 -(% style="margin-left: 30.0px;" %)
216 216  If data for a user already in the ONEcount system is being re-imported (e.g., to append information to his/her ONEcount profile) and:
217 -
218 -(% style="margin-left: 30.0px;" %)
219 -
220 -1) the user is imported to a product he/she is already subscribed to, and
149 + 1) the user is imported to a product he/she is already subscribed to, and
221 221  2) Expiration Date is specified
222 -\\The transaction will show as a renewal to the product and the earlier of the two expiration dates will be ignored. That is, if the expiration date specified in the import file is earlier than the expiration date already in ONEcount, the transaction will appear as a product renewal and the expiration date in ONEcount will not be changed. So, for example, if a user is already subscribed to "Print Magazine" product and the expiration date in ONEcount is 01-01-2015 and that same user is re-imported to that same product with an expiration date in the import file of 01-01-2014, the 01-01-2014 date will be ignored.
151 + The transaction will show as a renewal to the product and the earlier of the two expiration dates will be ignored. That is, if the expiration date specified in the import file is earlier than the expiration date already in ONEcount, the transaction will appear as a product renewal and the expiration date in ONEcount will not be changed. So, for example, if a user is already subscribed to "Print Magazine" product and the expiration date in ONEcount is 01-01-2015 and that same user is re-imported to that same product with an expiration date in the import file of 01-01-2014, the 01-01-2014 date will be ignored.
223 223  
224 -(% style="margin-left: 30.0px;" %)
225 -\\
153 +=== 8. To link media files for a record to the folder on your server where the media files are stored, select the column/field from your import file and the folder on your server where media files are stored.* ===
226 226  
227 -**8. To link media files for a record to the folder on your server where the media files are stored, select the column/field from your import file and the folder on your server where media files are stored.***
228 -
229 229  [[image:attach:8.__To_link_media_files_for_a_record_to_the_folder_on_you.png||align="center"]]
230 230  
231 231  *This server must be connected to ONEcount.
... ... @@ -236,20 +236,14 @@
236 236  
237 237  To link to a file stored on your server, e.g. scanned subscription/renewal cards, enter the path to the file in a column in your import file. Then select the folder on your server where the files are stored. This information will need to be provided to ONEcount so that it can be configured in the ONEcount back end and the folder selections displayed here.
238 238  
239 -\\
165 +=== 9. Click the "Set" button. ===
240 240  
241 -==== Set and Import ====
242 -
243 -**9. Click the "Set" button.**
244 -
245 245  [[image:attach:media_1443551680910.png||align="center"]]
246 246  
247 247  You can now either Save the Mapping (See "How to Create an Import Mapping Template" lesson), Import the file, or Reset the mapping.
248 248  
249 -\\
171 +=== 10. Click on the Import button. ===
250 250  
251 -**10. Click on the Import button.**
252 -
253 253  [[image:attach:media_1443551721550.png||align="center"]]
254 254  
255 255  The system will begin to process the import, and a Pre-Import Summary and Sample Mapping page will appear. (See screen shots and important information below.)
... ... @@ -258,260 +258,96 @@
258 258  
259 259  Clicking on "Save Mapping Template" will save the mappings to a template. See Mapping Template documentation for more detail.
260 260  
261 -\\
181 +=== 11. Review the Pre-Import Summary ===
262 262  
263 -==== Pre-Import Summary and Sample Mapping ====
264 -
265 -**~11. Review the Pre-Import Summary**
266 -
267 267  [[image:attach:11.__Review_the_Pre-Import_Summary.png||align="center"]]
268 268  
269 269  The system will alert you if there are records in your import file that match records in the ONEcount database based on the field(s) you select to check for duplicates. The pre-import summary screen will give you the number of new records to be imported (1), the number of duplicates (if any) in the import file (2), and the number of duplicates matched in the database (3).
270 270  
271 -{{tip}}
272 272  The number of "Duplicate Records in File" is how many records within the import file are already in the ONEcount database based on your selected field(s) to check for duplicates. **THIS IS NOT A COUNT OF THE NUMBER OF RECORDS //WITHIN// THE IMPORT FILE THAT ARE DUPLICATES.**
273 -{{/tip}}
274 274  
275 -{{tip}}
276 276  The number of "Duplicate Records Matched in Database" is the number of records within the database that match the field(s) you selected to check for duplicates.
277 -{{/tip}}
278 278  
279 -{{error}}
280 -(% style="color: rgb(0,51,102);" %)**The number of duplicates in the file and matched in the database should be the same. If there is a difference in the numbers, it's recommended NOT to process the duplicates but instead to go back and select an additional field(s) to check for duplicates or import the new records and download the duplicates for review prior to processing. (See example and screenshot below.)**
281 -{{/error}}
191 +(% style="color: rgb(255,0,0);" %)The number of duplicates in the file and matched in the database should be the same. If there is a difference in the numbers, it's recommended NOT to process the duplicates but instead to go back and select an additional field(s) to check for duplicates or import the new records and download the duplicates for review prior to processing. (See example and screenshot below.)
282 282  
283 283  (% style="color: rgb(0,0,0);" %)//**EXAMPLE**//(% style="color: rgb(196,0,0);" %):
284 284  
285 -(% style="margin-left: 30.0px;" %)
286 286  (% style="color: rgb(0,0,0);" %)You check for duplicates across email.
287 287  
288 -(% style="margin-left: 30.0px;" %)
289 289  (% style="color: rgb(0,0,0);" %)The import file contains one record with a blank email field and three records that are already in the ONEcount database.
290 290  
291 -(% style="margin-left: 30.0px;" %)
292 292  (% style="color: rgb(0,0,0);" %)There are six records with blank email fields in the ONEcount database.
293 293  
294 -(% style="margin-left: 30.0px;" %)
295 295  (% style="color: rgb(0,0,0);" %)ONEcount will identify the one record in the import file and the six recordsin ONEcount as duplicates (because they all have a blank email, which matches the record being imported).
296 296  
297 -(% style="margin-left: 30.0px;" %)
298 298  (% style="color: rgb(0,0,0);" %)The system will also identify the three records in the import file that already exist in the ONEcount database as duplicates.
299 299  
300 -(% style="margin-left: 30.0px;" %)
301 301  (% style="color: rgb(0,0,0);" %)The pre-import summary would say:
302 302  
303 -(% style="margin-left: 30.0px;" %)
304 304  (% style="color: rgb(0,0,0);" %)Duplicate records in file = 4 (the 1 with the blank email and the 3 already in the ONEcount database), and
305 305  
306 -(% style="margin-left: 30.0px;" %)
307 307  (% style="color: rgb(0,0,0);" %)Duplicate records matched in the database = 9 (the 6 records with blank emails in the ONEcount database plus the 3 records that are already in the ONEcount database). See screenshot below.
308 308  
309 -(% style="margin-left: 30.0px;" %)
310 310  (% style="color: rgb(0,0,0);" %)If you check across at least one other field, say **last name**, a record in the upload file and a record in the ONEcount database – each with an empty email field but with a last name – will not be considered duplicates unless they have an empty email field AND the same last name.
311 311  
312 312  [[image:attach:media_1366813790837.png||align="center"]]
313 313  
314 -\\
215 +=== 12. Review the Sample Mapping ===
315 315  
316 -**12. Review the Sample Mapping**
317 -
318 318  [[image:attach:12.__Review_the_Sample_Mapping.png||align="center"]]
319 319  
320 320  Sample Mapping gives you a preview of the data import. Five records will be displayed, each including the data from the import file and the field within ONEcount that it will be imported to. In the example above, the email address "spongy@bob.com" will be imported into the Email Address field in the ONEcount database, the first name "spongebob" will be imported into the First Name field in the ONEcout database, and the last name "squarepants" will be imported into the Last Name field in the ONEcount database. No data is shown in the "State Licensed" field, indicating that that field in the import file was empty.
321 321  
322 -(% style="color: rgb(230,0,0);" %)** **
221 +(% style="color: rgb(230,0,0);" %)**If a record(s) has a blank field in an import file and the record already exists in ONEcount with data in that same field, the data in the corresponding field in ONEcount will NOT be written over with a blank, even if the Request Date of the import is more recent than the date the information was entered into the ONEcount database.**
323 323  
324 -{{tip}}
325 -(% style="color: rgb(0,51,102);" %)**If a record(s) has a blank field in an import file and the record already exists in ONEcount with data in that same field, the data in the corresponding field in ONEcount will NOT be written over with a blank, even if the Request Date of the import is more recent than the date the information was entered into the ONEcount database.**
223 +(% style="color: rgb(255,0,0);" %)**If a record has "Null" in a field in the import file and the record already exists in ONEcount with data in that same field, the data in the corresponding field in the ONEcount database WILL BE written over with a blank if the request date of the import is more recent than the date the informaton was entered into the ONEcount database. If the request date is older than the date the information was entered in the database, the corresponding field will NOT be written over with a blank.**
326 326  
327 -(% style="color: rgb(255,0,0);" %)** **
328 -{{/tip}}
225 +=== 13. If everything looks good in the Sample Mapping, click the "Proceed" button at the bottom of the page. ===
329 329  
330 -(% style="color: rgb(255,0,0);" %)** **
331 -
332 -{{tip}}
333 -**If a record has "Null" in a field in the import file and the record already exists in ONEcount with data in that same field, the data in the corresponding field in the ONEcount database WILL BE written over with a blank if the request date of the import is more recent than the date the informaton was entered into the ONEcount database. If the request date is older than the date the information was entered in the database, the corresponding field will NOT be written over with a blank.**
334 -
335 -(% style="color: rgb(255,0,0);" %)** **
336 -{{/tip}}
337 -
338 -(% style="color: rgb(255,0,0);" %)**
339 -**
340 -
341 -**13. If everything looks good in the Sample Mapping, click the "Proceed" button at the bottom of the page.**
342 -
343 343  [[image:attach:media_1443552112267.png||align="center"]]
344 344  
345 345  All new records will be imported into ONEcount, and a post-import summary will be displayed.
346 346  
347 -==== Post-Import Summary ====
231 +=== 14. Review the Post-Import Summary and Download Lists of Duplicates and/or Process Duplicates. (See important information below.) ===
348 348  
349 -**14. Review the Post-Import Summary and Download Lists of Duplicates and/or Process Duplicates. (See important information below.)**
350 -
351 351  [[image:attach:media_1443552145622.png||align="center"]]
352 352  
353 353  The screenshot above shows a post-import summary without any duplicates, so at this point the import is complete.
354 354  
355 -The screenshot below shows a post-import summary with duplicates, and the total matched duplicates in the database and the total duplicates in the file don't match. At this point, you have the option to either Download Duplicates in the File, Download Duplicates in ONEcount, or Process Duplicates.
237 +The screenshot below shows a post-import summary with duplicates, and the total matched duplicates in the database and the total duplicates in the file don't match. At this point, you have the option to either Download Duplicates in the File, Downlod Duplicates in ONEcount, or Process Duplicates.
356 356  
357 -\\
239 +=== a. "Download Duplicates in file" and "Download Duplicates in ONEcount" ===
358 358  
359 -(% style="margin-left: 30.0px;" %)
360 -**a. "__Download Duplicates in file" and "Download Duplicates in ONEcount"__**
361 -
362 -(% style="margin-left: 60.0px;" %)
363 363  [[image:attach:media_1443552610096.png||align="center"]]
364 364  
365 -(% style="margin-left: 60.0px;" %)
366 366  (% style="color: rgb(0,0,0);" %)**Download Duplicates in file** will create a .csv file of all the records in the import file that have been identified as duplicates of records in the ONEcount database, based on the field(s) you selected to check duplicates.
367 367  
368 -(% style="margin-left: 60.0px;" %)
369 369  (% style="color: rgb(0,0,0);" %)**Download Duplicates in ONEount** will create a .csv file of all the records in ONEcount that have been identified as duplicates of records in the import file, based on the field(s) you selected to check duplicates.
370 370  
371 -(% style="margin-left: 60.0px;" %)
247 +(% style="color: rgb(0,0,0);" %)**Process Duplicates **will update the records in the ONEcount database identified as duplicates of records in the import file.
248 +
372 372  (% style="color: rgb(0,0,0);" %)You can download duplicates both in the file and in ONEcount and review. This window will remain open, so after review you can either process the duplicates or quit if you don't want to process at that time. (%%)
373 373  (% style="color: rgb(0,0,0);" %)Note that if you leave the window open for too long, you'll be logged out of ONEcount and will need to log back in to continue.
374 374  
375 -(% style="margin-left: 60.0px;" %)
376 376  (% style="color: rgb(0,0,0);" %)**Using the Example from Step 11 above:**(%%)
377 -(% style="color: rgb(0,0,0);" %)"Download Duplicates in ONEcount" will create a .csv file of the 9 records in ONEcount that are identified as duplicates of records in the import file.
378 -\\Using the example in Step 11 above, **6** of the duplicates will have a blank email field (which matches the one record in the import file without an email) and **3** will be records that match the email addresses of 3 records in the import file.
253 + (% style="color: rgb(0,0,0);" %)"Download Duplicates in ONEcount" will create a .csv file of the 9 records in ONEcount that are identified as duplicates of records in the import file. Using the example in Step 11 above, **6** of the duplicates will have a blank email field (which matches the one record in the import file without an email) and **3** will be records that match the email addresses of 3 records in the import file.
379 379  
380 -(% style="margin-left: 60.0px;" %)
381 381  "Download Duplicates in the file" will create a .csv file of the 4 records in the import file that are already in the ONEcount database: (% style="color: rgb(0,0,0);" %)the **1** record with the blank email (whicht matches the 6 records with blank email field in ONEcount) and the 3 that match the email addresses of **3** records already in the ONEcount database.
382 382  
383 -(% style="margin-left: 60.0px;" %)
384 -(% style="color: rgb(0,0,0);" %)T(%%)he import window will remain open so you can process the duplicates after reviewing the list if you choose to do so.
257 +(% style="color: rgb(0,0,0);" %)T(%%)he import window will remain open so you can process the duplicates after reviewing the list if you choose to do so. (% style="color: rgb(255,0,0);" %)**It is recommended to review the list of duplicates both in the file and ine ONEcount prior to processing them in a situation where the numbers of Total Matched Duplicates in the Database and the Total Duplicates in the File don't match.**
385 385  
386 -\\
259 +(% style="color: rgb(255,0,0);" %)If you didn't set a Request Date or the Request Date you selected is newer than the information in the ONEcount database and then you opt to "Process Duplicates", all of the mapped fields for the six records with a blank email field in the ONEcount database will be written over with the information from the ONE record with the blank email field in the upload file, AND the three records identified by email as already being in the ONEcount database will be written over with the corresponding data for those records in the import file.
387 387  
388 -{{error}}
389 -It is recommended to review the list of duplicates both in the file and in ONEcount prior to processing them in a situation where the numbers of Total Matched Duplicates in the Database and the Total Duplicates in the File don't match.
390 -{{/error}}
261 +(% style="color: rgb(0,0,0);" %)//If processing duplicates, selecting a request date on import ensures that only data in the ONEcount database that is older than data in the import file will be written over. ONEcount will compare the request date to the date of the most recent information in the database and only write over information that is older than the request date. This is done on a field-by-field basis within a record.//
391 391  
392 -{{error}}
393 -If you didn't set a Request Date or the Request Date you selected is newer than the information in the ONEcount database and then you opt to "Process Duplicates", all of the mapped fields for the six records with a blank email field in the ONEcount database will be written over with the information from the ONE record with the blank email field in the upload file, AND the three records identified by email as already being in the ONEcount database will be written over with the corresponding data for those records in the import file.
394 -{{/error}}
395 -
396 -{{tip}}
397 -If processing duplicates, selecting a request date on import ensures that only data in the ONEcount database that is older than data in the import file will be written over. ONEcount will compare the request date to the date of the most recent information in the database and only write over information that is older than the request date. This is done on a field-by-field basis within a record.
398 -{{/tip}}
399 -
400 -\\
401 -
402 -(% style="margin-left: 30.0px;" %)
403 403  (% style="color: rgb(0,0,0);" %)If there are, say, three records with a blank email field in the import file, then the mapped fields for the six records with a blank email field in the ONEcount database will be written over with the information from the last record with a blank email field in the import file.
404 404  
405 -(% style="margin-left: 30.0px;" %)
406 -(% style="color: rgb(0,0,0);" %)
265 +=== b. Process Duplicates ===
407 407  
408 -
409 -(% style="margin-left: 30.0px;" %)
410 -\\
411 -
412 -(% style="margin-left: 30.0px;" %)
413 -**b. __Process Duplicates__**
414 -
415 -(% style="margin-left: 30.0px;" %)
416 -(% style="color: rgb(0,0,0);" %)**Process Duplicates **will update the records in the ONEcount database identified as duplicates of records in the import file.
417 -
418 -(% style="margin-left: 30.0px;" %)
419 419  If you process duplicates, either with or without downloading and reviewing duplicates, the message below will appear when finished processing. At this point, your import is complete.
420 420  
421 -(% style="margin-left: 30.0px;" %)
422 422  [[image:attach:media_1443556620318.png||align="center"]]
423 423  
424 424  
425 425  
426 426  {{id name="End ScreenSteps Content"/}}
427 -{{/layout-cell}}
428 -
429 -{{layout-cell}}
430 -{{panel title="Search All Documentation:"}}
431 -
432 -
433 -{{livesearch/}}
434 -{{/panel}}
435 -
436 -{{panel title="Search USER OPERATIONS Documentation:"}}
437 -
438 -
439 -{{pagetreesearch rootPage="User Operations - Managing Your Data"/}}
440 -{{/panel}}
441 -
442 -{{panel title="On this page:"}}
443 -
444 -
445 -{{toc/}}
446 -{{/panel}}
447 -
448 -{{panel title="More USER OPERATIONS Documentation"}}
449 -{{expand}}
450 - **Add Users
451 -**
452 -
453 -(% style="margin-left: 60.0px;" %)
454 -
455 -
456 -(% style="margin-left: 60.0px;" %)
457 -[[Preparing for Data Import>>doc:Getting Started - Preparing for Data Import]]
458 -
459 -(% style="margin-left: 60.0px;" %)
460 -[[doc:Pre-Import Checklist]]
461 -
462 -(% style="margin-left: 60.0px;" %)
463 -
464 -
465 -(% style="margin-left: 60.0px;" %)
466 -[[How to Create an Import Mapping Template>>doc:Import - How to Create an Import Mapping Template]]
467 -
468 -(% style="margin-left: 60.0px;" %)
469 -[[How to Use an Import Mapping Template>>doc:Import - How to Use an Import Mapping Template]]
470 -
471 -(% style="margin-left: 60.0px;" %)
472 -[[doc:Add Audience]]
473 -
474 -(% style="margin-left: 30.0px;" %)
475 -**Batch Operations**
476 -
477 -(% style="margin-left: 60.0px;" %)
478 -[[doc:Bulk Operation - How to Perform a Batch Delete]]
479 -
480 -(% style="margin-left: 60.0px;" %)
481 -[[doc:Bulk Operation - How to Perform a Batch Product Change]]
482 -
483 -(% style="margin-left: 60.0px;" %)
484 -[[doc:Bulk Operation - How to Perform a Batch Status Change]]
485 -
486 -(% style="margin-left: 60.0px;" %)
487 -[[Bulk Operation - How to Perform a Batch Suscribe>>doc:Bulk Operation - How to Perform a Batch Subscribe]]
488 -
489 -(% style="margin-left: 60.0px;" %)
490 -[[Bulk Operation - How to Perform a Batch Unsubscribe>>doc:Bulk Operation - How to Perform a Batch UnsubscribeKill]]
491 -
492 -(% style="margin-left: 60.0px;" %)
493 -[[Bulk Operation - How to Perform a Merge of Duplicate Users>>doc:Bulk Operation - How to Perform a Bulk Merge of Duplicate Users]]
494 -
495 -(% style="margin-left: 30.0px;" %)
496 -**Target Audience Segments**
497 -
498 -(% style="margin-left: 60.0px;" %)
499 -(% style="color: rgb(0,51,102);" %) [[ Target Engine >>doc:Segment Manager]]__
500 -__
501 -
502 -\\
503 -
504 -\\
505 -{{/expand}}
506 -{{/panel}}
507 -
508 -\\
509 -
510 -\\
511 -
512 -\\
513 -
514 -\\
515 -{{/layout-cell}}
516 -{{/layout-section}}
517 -{{/layout}}
11.__Review_the_Pre-Import_Summary.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -32.0 KB
Content
12.__Review_the_Sample_Mapping.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -16.9 KB
Content
3b.__If_not_using_an_Import_Mapping_Template__The_mapping.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -27.1 KB
Content
4._Proceed_to_the_mapping_section_and_map_your_fields___1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -90.0 KB
Content
5.__DO_NOT_SKIP_THIS_STEP_--_ALWAYS_CHECK_FOR_DUPLICATES_.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -45.7 KB
Content
6.__Select_from_the_Request_Date_drop-down_menu_the_fie_1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -54.9 KB
Content
7.__Select_the_columnfield_in_your_import_file_to_specify.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -34.1 KB
Content
8.__To_link_media_files_for_a_record_to_the_folder_on_you.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -68.8 KB
Content
Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -15.2 KB
Content
Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -16.3 KB
Content
media_1362667166234.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -13.3 KB
Content
media_1366813790837.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -29.0 KB
Content
media_1406494045151.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -1.3 KB
Content
media_1443213231223.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -24.2 KB
Content
media_1443213261172.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -24.4 KB
Content
media_1443213294962.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -43.2 KB
Content
media_1443213396710.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -44.0 KB
Content
media_1443549296560.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -40.5 KB
Content
media_1443551680910.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -559 bytes
Content
media_1443551721550.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -3.7 KB
Content
media_1443552112267.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -856 bytes
Content
media_1443552145622.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -28.2 KB
Content
media_1443552610096.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -41.6 KB
Content
media_1443556620318.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -4.0 KB
Content
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -66546
1 +66920
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/66546/Import - How to Import a File
1 +https://info.onecount.net//wiki/spaces/OD/pages/66920/Import - How to Import a File (v12.x)