Hi there,
There is no set way to get the reference display copy included in the export CSV - by default, AtoM always includes the path to the digital object master. This is partially so that if you are importing it into another system, you are not treating the reference derivative as a new master!
However, there is one thing you could try: manually editing the path in the output CSVs. However, there are a LOT of potential problems with this approach, which I will outline below. For reference, you might want to look at this thread, where I outline how digital objects are stored in AtoM when uploaded:
Generally, for older uploads in earlier versions of AtoM, all the reference copies have the same URL, but with _141 appended to the file path before the file extension, and thumbnails are the same, but with _142 appended.
To take an example from our demo data: Here is a digital object master (remember you will probably need to be logged into our demo site to access this path):
To get the reference display copy, you could use:
And to get the thumbnail:
This becomes tricky, however, in a couple cases.
The first case is when it is a text document, such as a PDF. In that case, the reference display copy and the thumbnail are not actually PDF files - they are JPG files! So simply adding _141 will return a "page not found" message. Instead, you need to remember to change the file extension as well. An example:
The second case appears to be when Rights have been applied - in the example I found, it's when a copyright notice warning is triggered, as in this description:
If you are logged in and click on the digital object, you are first taken to the copyright notice page, and when you click ok, the link to the master object is:
The token is passed to indicate that the user has clicked OK on the copyright notice. If we have already clicked ok, then a cookie is stored, and we can remove the token, leaving us with this URL:
However, in this case, simply adding _141 or _142 doesn't work! In fact, here are the actual URLs for the reference copy and the thumbnail:
Finally, the third case I know of is when the master digital object is in fact an external link, such as the one on this description in our demo data:
In this case, the master object was linked, so when you click on the image, you are redirected to:
Obviously, just adding _141 or _142 won't work in this case! When digital objects are linked externally, AtoM does not store the master - instead it generates local derivatives and just points to the master. For this record, the local derivatives are actually stored at:
In this case, a hash has been applied - and notice that it is a different hash for the thumb and the reference copy!
Now, you'll notice that I said in older versions of AtoM - if you read the first linked thread above, you will see that I mention that "more recent versions of AtoM might actually include a 3rd nesting based on the third checksum value." This may mean that a full checksum hash is used for each copy - meaning the paths will be different. I haven't had an opportunity to test this in my local environment, but thought I would mention it! If that is the case, then unfortunately the workarounds I mentioned above may not work for you.
All this to say: To be able to get the reference image copy in the CSV export, we would likely need to do development to add a new column to add this information. Nevertheless, I hope that something here helps you find an approach that will work for your needs!
Regards,