basic URI question

[lda...@alumni.ubc.ca]

I am having trouble filling in the digitalObjectURI column on CSVs I am uploading into AtoM 2.3.1. I have a path that works fine in the browser (Explorer or Chrome) but that doesn't work in the CSV. This path is like K:\Scanned Documents\scanned\100\100 0006 v1.pdf. I tried messing with syntax and adding the scheme (ex. file:) and the name of the local host and using forward slashes. None of the things I did worked.

Is there a way to enter this path into the digitalObjectURI column?

Thanks!

[Dan Gillean]

Hi there,

A couple tips that might help:

First, it should use forward slashes  - e.g. path/to/my/file.pdf

Second, the digitalObjectURI column is to reference web accessible resources - so they begin with http:// and should be accessible on the web. It's likely that this path works in your browser because you have this network drive mounted on that specific computer - but would the same path work if you tried it from home?

You can add a column to the CSV import template called digitalObjectPath if you want to upload local content - however, in this case, the objects must be on the same server as AtoM, in a directory accessible to you from there - so if your AtoM instance is installed at /usr/share/nginx/atom, you could create a temporary folder called documents and add your digital objects there. In that case, your digitalObjectPath value might be /usr/share/nginx/atom/documents/1000 0006 v1.pdf - though I think you should be able to just refer to it in the CSV as documents/1000 0006 v1.pdf. I don't think that pointing at another drive - e.g. K: - is going to work, unfortunately.

In both cases, the path MUST end in a file extension - so you can't just point to a YouTube video page for example, because YouTube purposefully obfuscates the actual movie file so you can't download it directly by right-click and saving. If you were looking at an image on a webage, you would generally want to right-click and select "View image" (or whatever your browser's equivalent option is) to see the direct path to the object that ends in .jpg.

I hope that helps!

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/a51904ff-7576-4f54-a7e7-2f5baf489c64%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[lda...@alumni.ubc.ca]

This is the exact information I needed. Thanks.

On Thursday, May 25, 2017 at 1:47:34 PM UTC-7, Dan Gillean wrote:

Hi there,

A couple tips that might help:

First, it should use forward slashes  - e.g. path/to/my/file.pdf

Second, the digitalObjectURI column is to reference web accessible resources - so they begin with http:// and should be accessible on the web. It's likely that this path works in your browser because you have this network drive mounted on that specific computer - but would the same path work if you tried it from home?

You can add a column to the CSV import template called digitalObjectPath if you want to upload local content - however, in this case, the objects must be on the same server as AtoM, in a directory accessible to you from there - so if your AtoM instance is installed at /usr/share/nginx/atom, you could create a temporary folder called documents and add your digital objects there. In that case, your digitalObjectPath value might be /usr/share/nginx/atom/documents/1000 0006 v1.pdf - though I think you should be able to just refer to it in the CSV as documents/1000 0006 v1.pdf. I don't think that pointing at another drive - e.g. K: - is going to work, unfortunately.

In both cases, the path MUST end in a file extension - so you can't just point to a YouTube video page for example, because YouTube purposefully obfuscates the actual movie file so you can't download it directly by right-click and saving. If you were looking at an image on a webage, you would generally want to right-click and select "View image" (or whatever your browser's equivalent option is) to see the direct path to the object that ends in .jpg.

I hope that helps!

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

On Thu, May 25, 2017 at 4:28 PM, <lda...@alumni.ubc.ca> wrote:

I am having trouble filling in the digitalObjectURI column on CSVs I am uploading into AtoM 2.3.1. I have a path that works fine in the browser (Explorer or Chrome) but that doesn't work in the CSV. This path is like K:\Scanned Documents\scanned\100\100 0006 v1.pdf. I tried messing with syntax and adding the scheme (ex. file:) and the name of the local host and using forward slashes. None of the things I did worked.

Is there a way to enter this path into the digitalObjectURI column?

Thanks!

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.

[lda...@alumni.ubc.ca]

Actually, one more thing. Can I add the digitalObjectPATH column at the end of the CSV or just replace the digitalObjectURI column?

On Thursday, May 25, 2017 at 1:47:34 PM UTC-7, Dan Gillean wrote:

Hi there,

A couple tips that might help:

First, it should use forward slashes  - e.g. path/to/my/file.pdf

Second, the digitalObjectURI column is to reference web accessible resources - so they begin with http:// and should be accessible on the web. It's likely that this path works in your browser because you have this network drive mounted on that specific computer - but would the same path work if you tried it from home?

You can add a column to the CSV import template called digitalObjectPath if you want to upload local content - however, in this case, the objects must be on the same server as AtoM, in a directory accessible to you from there - so if your AtoM instance is installed at /usr/share/nginx/atom, you could create a temporary folder called documents and add your digital objects there. In that case, your digitalObjectPath value might be /usr/share/nginx/atom/documents/1000 0006 v1.pdf - though I think you should be able to just refer to it in the CSV as documents/1000 0006 v1.pdf. I don't think that pointing at another drive - e.g. K: - is going to work, unfortunately.

In both cases, the path MUST end in a file extension - so you can't just point to a YouTube video page for example, because YouTube purposefully obfuscates the actual movie file so you can't download it directly by right-click and saving. If you were looking at an image on a webage, you would generally want to right-click and select "View image" (or whatever your browser's equivalent option is) to see the direct path to the object that ends in .jpg.

I hope that helps!

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

On Thu, May 25, 2017 at 4:28 PM, <lda...@alumni.ubc.ca> wrote:

I am having trouble filling in the digitalObjectURI column on CSVs I am uploading into AtoM 2.3.1. I have a path that works fine in the browser (Explorer or Chrome) but that doesn't work in the CSV. This path is like K:\Scanned Documents\scanned\100\100 0006 v1.pdf. I tried messing with syntax and adding the scheme (ex. file:) and the name of the local host and using forward slashes. None of the things I did worked.

Is there a way to enter this path into the digitalObjectURI column?

Thanks!

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.