Welcome to the AtoM community!
Regarding question 1:
That's a mistake! It looks like it's in the version stored in AtoM as well. I've fixed this now on the wiki
, and in our codebase
, so the updated template will be included in our 2.7 release.
Regarding question 2:
You can remove columns you aren't using from the CSV, but AtoM will expect the column headers provided in the example CSVs to be able to recognize the data and import it. It would be possible to develop a local transformation script so you can use your own template, and then transform it into AtoM's expected format before importing - but that requires development and maintenance of a transformation script, and it's a fair bit of effort for your own custom column names! I'd wager it would be easier to draft up some local documentation for your staff to use, providing some guidance - or create your own example row in the CSV template that can be used as a reference, and deleted before importing.