Re: [Archivesspace_Users_Group] copyright/licensing statements in finding aids

I just wanted to say that I'm so glad that you brought this up, and that TS-DACS has been considering adding this to the content standard for some time now. In my opinion, there's no meaningful place for this in ArchivesSpace right now. But since ArchivesSpace (nominally) aligns with DACS, perhaps

[Archivesspace_Users_Group] copyright/licensing statements in finding aids

We would like to apply a Creative Commons license to the resource records we create in and finding aids we generate from ArchivesSpace. Is anyone else already doing this, and if so, where are you entering that information in ArchivesSpace? I had originally thought of putting that

[Archivesspace_Users_Group] JIRA issues cleanup ? [was: Enumerations Findings]

BTW: I know there’s been a recent changing of the guard, so cleanup of JIRA issues may have been neglected, but on this subject: I believe ar-1421 and ar-647 can both be marked as closed ( and probably several others. Or is this status being tracked somewhere else? )

Re: [Archivesspace_Users_Group] XLink value question for DO Instance File Version

It’s the spaces in the URL which are causing it to fail converting the string to a URI. [2] pry(main)> u=URI( 'http://abc/def ghi xxx.pdf' ) URI::InvalidURIError: bad URI(is not URI?): http://abc/def ghi xxx.pdf from /usr/local/var/rbenv/versions/jruby-1.7.24/lib/ruby/1.9/uri/common.rb:176:in

Re: [Archivesspace_Users_Group] Enumerations Findings

Same here: doesn’t look like UTF-8 to me. Tried converting it with 'iconv -f LATIN1 -t UTF-8’ and importing it doesn’t give an character encoding error. It does give me ‘accession date : Not a valid date’ error. ( This is on v1.4.2 which is what I’m running some test on now. ) — Steve. On

Re: [Archivesspace_Users_Group] Enumerations Findings

I've attached the .csv example. I didn't test it in 1.5.3, but the bug occurs in 1.5.2 (I know it did not occur in 1.5.1). I reported the bug on January 17. On Wed, Feb 15, 2017 at 3:04 PM, Majewski, Steven Dennis (sdm7g) < sd...@eservices.virginia.edu> wrote: > Yes, and the previous cases I’ve

Re: [Archivesspace_Users_Group] Enumerations Findings

Yes, and the previous cases I’ve seen ( which have since been fixed ) have been where the document was originally parsed with correct character encoding, but that encoding wasn’t being preserved on some other ( xml or json ) internal transform. So that might be something to look for if it’s

Re: [Archivesspace_Users_Group] XLink value question for DO Instance File Version

Screenshot attached. Yes, full URLs. Kari R. Smith Digital Archivist and Program Head for Born-digital Archives Institute Archives and Special Collections Massachusetts Institute of Technology Libraries, Cambridge, Massachusetts 617.253.5690 smithkr at mit.edu

Re: [Archivesspace_Users_Group] XLink value question for DO Instance File Version

Are they full http:|https: URLs ? ( I know there’s some code that, if there is no scheme in the URLs, assumes they are file: URLs and prepends that scheme. That, and some Windows specific backslash hacks should probably be redone. ) Can you give example of the URLs and maybe a screen shot ? —

Re: [Archivesspace_Users_Group] Public access of finding aids

Simple pricing, mostly turnkey: https://libraryhost.com/pricing On Wed, Feb 15, 2017 at 1:01 PM -0500, "Kari R Smith" wrote: Hi Odette,   Check the information on the ArchviesSpace.org website of Registered Service Providers.

[Archivesspace_Users_Group] XLink value question for DO Instance File Version

Hi all, I'm having trouble getting my URLs in the File Version data field to be an actual hyperlinked URL and could use some help. My XLink Actuate is OnLoad XLink Show is embed The behavior I would like to have is for there to be a hyperlink to the digital object but the full URI not display

Re: [Archivesspace_Users_Group] Enumerations Findings

Do you have a sample import file that fails this way ? Do you know if it still fail on current release ? ( and is bug reported on Jira ? ) — Steve. On Feb 15, 2017, at 3:25 PM, Lisa Calahan > wrote: I've also received the same UTF8 error when

Re: [Archivesspace_Users_Group] Enumerations Findings

I've also received the same UTF8 error when importing legacy accession records that have *valid* diacritical marks in the title and/or agent name. Lisa On Wed, Feb 15, 2017 at 2:17 PM, Reese, Terry P. wrote: > I guess my question would be – is your legacy data UTF8? For

Re: [Archivesspace_Users_Group] Enumerations Findings

I totally agree that we shouldn’t have special characters if at all possible, but a large amount of our legacy data uses them. Especially in titles, staff want to use those characters as they are reflected on original materials. Suzanne From:

Re: [Archivesspace_Users_Group] Enumerations Findings

This also came up for me recently. If invalid special characters are present in the content titles, I get this error. I’m not sure quite how to adjust to accept those special characters. [cid:image001.png@01D2879B.058D6980] Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum

[Archivesspace_Users_Group] ArchivesSpace v1.5.3 released

The ArchivesSpace team is very pleased to release version 1.5.3! You can download the new release from Github at https://github.com/archivesspace/archivesspace/releases/tag/v1.5.3. This minor release has some bug fixes, including a fix for the issue with resource components being exported

[Archivesspace_Users_Group] Hiding Controlled Date Fields

Since implementing automated date parsing in ASpace and our discovery system, we don't have a local need for the controlled date fields in ASpace's Date sub-form. As such, we'd like to prevent the controlled date fields from spawning in the data entry interface via a plug-in. It seems that the