1SCORELib
Is there any way to remove the default fields from the mapping process? We only want patron name, barcode/id, and three custom fields. Yet email, phone, address 1 and 2, etc fields keep appearing under Patron Fields between barcode/id and our custom fields. We already unchecked these fields in our Patrons settings, but they keep appearing as fields we need to map. So we either need to add a bunch of empty columns in our csv file or drag them all to the bottom. Is there any way to make them just not appear during this step? We would like to streamline the process of creating patron accounts.
2ZephCraven
>1 SCORELib: Hi there! Happy to help. There's not a way to customize the mapping process itself.
Are you always adding patrons in bulk? While patron import can read many spreadsheets with decent success, it is designed to be used with the sample patron import spreadsheet which you can see in the import pop-up. I recommend that, when you're importing patrons en masse, you use the sample spreadsheet as a template and paste your patron info there so that it matches up with the import fields more closely. The import mapping is more about making sure we can read the file and organizing the info in it to the proper place. Imports can be tricky, so we have to keep the design pretty universal so that imports can be successful for a variety of libraries' needs.
If you're not adding patrons in bulk every time, then you'll probably find it easier to add a patron or two using the Add Patron button. That pop-up form should only include your preferred patron fields, rather than referencing the standard import fields.
Please let me know if you have any other questions about this!
Are you always adding patrons in bulk? While patron import can read many spreadsheets with decent success, it is designed to be used with the sample patron import spreadsheet which you can see in the import pop-up. I recommend that, when you're importing patrons en masse, you use the sample spreadsheet as a template and paste your patron info there so that it matches up with the import fields more closely. The import mapping is more about making sure we can read the file and organizing the info in it to the proper place. Imports can be tricky, so we have to keep the design pretty universal so that imports can be successful for a variety of libraries' needs.
If you're not adding patrons in bulk every time, then you'll probably find it easier to add a patron or two using the Add Patron button. That pop-up form should only include your preferred patron fields, rather than referencing the standard import fields.
Please let me know if you have any other questions about this!
