Re: [Archivesspace_Users_Group] Digital Object vs Resource record

[Jacob, Diane B]

Barbara,

We have many digital objects and have decided on a compromise with regard to 
description.  We have customized the DO record label so that it contains a user 
friendly "Full Description" header that is prominent.  This links back to the 
complete collection.
https://archivesspace.vmi.edu/repositories/3/digital_objects/185
We don't repeat all of the information from the resource record, but only key 
pointers.

Diane

Diane B. Jacob
Head, Archives & Records Management
Virginia Military Institute
Preston Library
Lexington, VA 24450
540-464-7566
www.vmi.edu/archives

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Benedett, Barbara
Sent: Monday, November 13, 2017 1:15 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Digital Object vs Resource record


Hello,



I'm curious about how people are handling digital objects attached to resources 
in ASpace.  If you have created an archival object for which you will attach a 
digital object as an instance, where do you tend to put the bulk of the 
descriptive metadata?  Or do you duplicate notes and/or children in both the DO 
and the resource record?  How about DO's dates?  Do you tend to record only the 
date the digital object was created or the dates of the digitized materials 
within as well?



I am, of course, reluctant to have to type the same data twice.  However, since 
I will be publishing many of the DOs for public view, I'm inclined to want the 
same level of detail in both the finding aid and the digital object record.  
Anyone care to share what you do in this area?



Thanks,

Barbara





Barbara J. Benedett, CA

Digital Archivist | Rock Resource Center

1720 Locust Street, Philadelphia, PA 19103

(215) 717-3139 Phone  |  (215) 893-9065 Fax  |  
barbara.bened...@curtis.edu





[logo gif not for paper (horizontal)]






___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] digital objects

[Tang, Lydia]

Hi all,
Although SIEWG didn’t particularly focus on recommendations for digital objects 
(in terms of the staff interface), I would be very interested in your ideas.  
Many of the volunteers (including myself) haven’t yet dug into that area at our 
institutions, so if people have ideas on how creating/editing/importing digital 
objects into ArchivesSpace could be improved, maybe it would be a good idea to 
use the SIEWG brainstorm 
page
 to start hashing out ideas?  Screen shots and wireframes are highly 
encouraged.  This page just contains ideas that aren’t fully fleshed out yet as 
recommendations.
Brainstorming: 
https://docs.google.com/document/d/1ZQwFowMnUx8AIiewqbqO08CO9TSGIe22AnYCUza9LEo/edit?usp=sharing

SIEWG recommendations Table of Contents (with links to access the rest of our 
documentation).
https://docs.google.com/document/d/1cCyUsZ0wR1D3irffoJIAbdlXaU8egPuLG-ld6fERdPo/edit?usp=sharing

If you have feedback for our recommendations as well, we would love to hear 
from you.
Thanks, all!  And thank you to everyone who chimed in earlier about my other 
questions!
Lydia

From:  on behalf of 
"Rees, John (NIH/NLM) [E]" 
Reply-To: Archivesspace Users Group 

Date: Monday, November 13, 2017 at 9:39 AM
To: Archivesspace Users Group 
Subject: *SPAM*Re: [Archivesspace_Users_Group] batch delete dates saga 
continues

Along this line I’ve been struggling with finding an authoritative data 
dictionary for all of ASpace’s model classes and all the possible endpoint 
parameters. The API documentation provides much of this but not seemingly all, 
esp. mixins.

For example: I would like an application developer to modify the Digital Object 
CSV importer to add specific Note fields that do not exist in the DO import 
template or data map at 
http://archivesspace.org/using-archivesspace/migration-tools-and-data-mapping/. 
I can’t reasonably expect a developer to “learn by doing”, read code or test 
documents, or watch YouTube videos -- nor will their managers allow them to do 
any of that.

Having such an authoritative data dictionary would help to build external 
stakeholder confidence in ASpace as a documented, robust, authoritative data 
management application.

Or perhaps I’m missing some boat entirely?

John

John P. Rees
Archivist and Digital Resources Manager
History of Medicine Division
National Library of Medicine
301-827-4510



From: Galligan, Patrick [mailto:pgalli...@rockarch.org]
Sent: Monday, November 13, 2017 9:14 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

Hey all,

I think a great place to get started learning about Python, APIs, and 
ArchivesSpace would be some of the API tutorials that members of the 
ArchivesSpace community have taught.

Lora Woodford from JHU taught a workshop about 4 months ago and made the 
materials available on Github: 
https://github.com/jhu-archives-and-manuscripts/ASpace_API_Workshop.

Personally, I’ve found that I learn best by doing. So I learned what I did 
about the AS JSON responses by downloading Postman 
(https://www.getpostman.com/) and performing a few API calls against our 
development database. Also, back in 2014, Maureen Callahan and a few other 
archivists ran a blog about dealing with legacy data. They have some posts 
about AS API work. I personally liked this post as a beginner: 
https://icantiemyownshoes.wordpress.com/2014/08/01/a-very-brief-guide-to-deleting-records-with-the-archivesspace-api-from-a-total-tyro/.

This is a great resource for learning python: 
https://automatetheboringstuff.com/.

I’m sure there are a ton of other resources out there, but those are the few 
off the top of my head. I’m willing to jump in and give some more 
recommendations as needed.

-Patrick Galligan

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Margaret Kidd
Sent: Friday, November 10, 2017 5:31 PM
To: Archivesspace Users Group 
>
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

I second that last part of Lydia's remarks about where to begin learning more 
about XML, JSON, python, ruby, etc. and applying it to ArchivesSpace. I want to 
learn, but it is overwhelming to know where to begin and my time to devote to 
it is rather limited. Every time I start trying to teach myself I have other 
work priorities that take up all my time and soon forget whatever progress I 
have made.

[Archivesspace_Users_Group] Digital Object vs Resource record

[Benedett, Barbara]

Hello,



I’m curious about how people are handling digital objects attached to resources 
in ASpace.  If you have created an archival object for which you will attach a 
digital object as an instance, where do you tend to put the bulk of the 
descriptive metadata?  Or do you duplicate notes and/or children in both the DO 
and the resource record?  How about DO’s dates?  Do you tend to record only the 
date the digital object was created or the dates of the digitized materials 
within as well?



I am, of course, reluctant to have to type the same data twice.  However, since 
I will be publishing many of the DOs for public view, I’m inclined to want the 
same level of detail in both the finding aid and the digital object record.  
Anyone care to share what you do in this area?



Thanks,

Barbara





Barbara J. Benedett, CA

Digital Archivist | Rock Resource Center

1720 Locust Street, Philadelphia, PA 19103

(215) 717-3139 Phone  |  (215) 893-9065 Fax  |  
barbara.bened...@curtis.edu





[logo gif not for paper (horizontal)]






___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] batch delete dates saga continues

[Lora Woodford]

Hey and thanks for the plug, Patrick!

My co-workshop lead, Valerie Addonizio, and I tried to make the resources we 
put up in that GitHub stand on their own without the in-person part of the 
workshop.  It was really important to us that everyone – not just those able to 
get to and pay for a 1-day workshop – be able to tinker about.  As Patrick has 
said, tinkering is the BEST way to learn.  It’s certainly how I did.  If anyone 
wants assistance in working through these workshop materials, definitely give a 
shout.  Like all of the rest of you, I have a super busy day job, but I’m happy 
to help as time allows!

Regarding the time to do this, everyone’s situation is going to be different, 
but if your institution supports the idea of professional development 
time/personal goals, it can be a good idea to talk about this with supervisors 
and make it an articulated part of your job.  Last year my “personal goal” was 
to increase my proficiency with Rails, so I tried to set aside an hour or so 
every couple weeks to dedicate myself to that, in the same way that I try to 
stay on top of the literature in ours and allied fields. Your learning style 
may vary, but I find it is best to just set aside a little bit of time over a 
long period, rather than trying to “cram” everything at once. Approach it as 
you would approach learning a foreign language. You aren’t going to do it in 
one weekend, one month, or, even, one year. It will grow naturally over time as 
you expose yourself to it. There are SO MANY wonderful resources out there 
(most for free), and you’ve got a community of folks who can help connect you 
to them. I won’t go too much into specifics as my answers will vary depending 
on what you want to do/what your specific setup looks like, but Code Academy, 
Lynda.com, the Hitchhiker’s Guide to Python 
(http://docs.python-guide.org/en/latest/), and some of the “better” coding boot 
camps (https://www.switchup.org/research/best-coding-bootcamps) offer free 
online courses (but, be forewarned, if you sign up with one of them they WILL 
hound you to apply to their programs and actively try and recruit you to their 
school ;-) ).

Good luck, all,

Lora

--
Lora J. Woodford
The Sheridan Libraries
Johns Hopkins University
3400 North Charles Street
Baltimore, MD 21228
(410) 516-5898
lwoodf...@jhu.edu

From:  on behalf of 
"Galligan, Patrick" 
Reply-To: Archivesspace Users Group 

Date: Monday, November 13, 2017 at 9:52 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

Hey all,

I think a great place to get started learning about Python, APIs, and 
ArchivesSpace would be some of the API tutorials that members of the 
ArchivesSpace community have taught.

Lora Woodford from JHU taught a workshop about 4 months ago and made the 
materials available on Github: 
https://github.com/jhu-archives-and-manuscripts/ASpace_API_Workshop.

Personally, I’ve found that I learn best by doing. So I learned what I did 
about the AS JSON responses by downloading Postman 
(https://www.getpostman.com/) and performing a few API calls against our 
development database. Also, back in 2014, Maureen Callahan and a few other 
archivists ran a blog about dealing with legacy data. They have some posts 
about AS API work. I personally liked this post as a beginner: 
https://icantiemyownshoes.wordpress.com/2014/08/01/a-very-brief-guide-to-deleting-records-with-the-archivesspace-api-from-a-total-tyro/.

This is a great resource for learning python: 
https://automatetheboringstuff.com/.

I’m sure there are a ton of other resources out there, but those are the few 
off the top of my head. I’m willing to jump in and give some more 
recommendations as needed.

-Patrick Galligan

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Margaret Kidd
Sent: Friday, November 10, 2017 5:31 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

I second that last part of Lydia's remarks about where to begin learning more 
about XML, JSON, python, ruby, etc. and applying it to ArchivesSpace. I want to 
learn, but it is overwhelming to know where to begin and my time to devote to 
it is rather limited. Every time I start trying to teach myself I have other 
work priorities that take up all my time and soon forget whatever progress I 
have made.

Thanks,

Margaret




Margaret T. Kidd

Project Archivist, Special Collections & Archives

VCU Libraries | Tompkins-McCaw Library for the Health Sciences

509 N. 12th Street / Box 980582, Richmond, VA 23298-0582

(804) 828-3152

Re: [Archivesspace_Users_Group] batch delete dates saga continues

[Rees, John (NIH/NLM) [E]]

Along this line I’ve been struggling with finding an authoritative data 
dictionary for all of ASpace’s model classes and all the possible endpoint 
parameters. The API documentation provides much of this but not seemingly all, 
esp. mixins.

For example: I would like an application developer to modify the Digital Object 
CSV importer to add specific Note fields that do not exist in the DO import 
template or data map at 
http://archivesspace.org/using-archivesspace/migration-tools-and-data-mapping/. 
I can’t reasonably expect a developer to “learn by doing”, read code or test 
documents, or watch YouTube videos -- nor will their managers allow them to do 
any of that.

Having such an authoritative data dictionary would help to build external 
stakeholder confidence in ASpace as a documented, robust, authoritative data 
management application.

Or perhaps I’m missing some boat entirely?

John

John P. Rees
Archivist and Digital Resources Manager
History of Medicine Division
National Library of Medicine
301-827-4510



From: Galligan, Patrick [mailto:pgalli...@rockarch.org]
Sent: Monday, November 13, 2017 9:14 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

Hey all,

I think a great place to get started learning about Python, APIs, and 
ArchivesSpace would be some of the API tutorials that members of the 
ArchivesSpace community have taught.

Lora Woodford from JHU taught a workshop about 4 months ago and made the 
materials available on Github: 
https://github.com/jhu-archives-and-manuscripts/ASpace_API_Workshop.

Personally, I’ve found that I learn best by doing. So I learned what I did 
about the AS JSON responses by downloading Postman 
(https://www.getpostman.com/) and performing a few API calls against our 
development database. Also, back in 2014, Maureen Callahan and a few other 
archivists ran a blog about dealing with legacy data. They have some posts 
about AS API work. I personally liked this post as a beginner: 
https://icantiemyownshoes.wordpress.com/2014/08/01/a-very-brief-guide-to-deleting-records-with-the-archivesspace-api-from-a-total-tyro/.

This is a great resource for learning python: 
https://automatetheboringstuff.com/.

I’m sure there are a ton of other resources out there, but those are the few 
off the top of my head. I’m willing to jump in and give some more 
recommendations as needed.

-Patrick Galligan

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Margaret Kidd
Sent: Friday, November 10, 2017 5:31 PM
To: Archivesspace Users Group 
>
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

I second that last part of Lydia's remarks about where to begin learning more 
about XML, JSON, python, ruby, etc. and applying it to ArchivesSpace. I want to 
learn, but it is overwhelming to know where to begin and my time to devote to 
it is rather limited. Every time I start trying to teach myself I have other 
work priorities that take up all my time and soon forget whatever progress I 
have made.

Thanks,

Margaret




Margaret T. Kidd

Project Archivist, Special Collections & Archives

VCU Libraries | Tompkins-McCaw Library for the Health Sciences

509 N. 12th Street / Box 980582, Richmond, VA 23298-0582

(804) 828-3152
[em_twitter.png][em_fb.png]


[http://identity.vcu.edu/images/photos/vcu_brand_mark_email_sig.jpg]
 
[http://pages.shanti.virginia.edu/Virginia_Heritage/files/2013/01/vhpban.jpg] 



On Fri, Nov 10, 2017 at 12:02 PM, Tang, Lydia 
> wrote:
Mark,
Thank you for identifying my problem!  Just for the sake of technological 
dummies like me, what should I do?  Everything there (besides removing the 
 tags is exactly as it spat out of ArchivesSpace, so I wonder if the 
export allowed the invalid characters?  I also wonder if the importing process 
could be improved within the ArchivesSpace code to search for “aspace_" and not 
batch add it as well as recognize (or not export out in the first place) the 
"Linear Feet" / linear_feet controlled vocabulary?  Ideally, after establishing 
with the database that linear_feet should publish as Linear Feet, I wish it 
would continue to recognize that rule when new stuff is imported in.
I was also meaning poll people on “how do I even get started” with learning 
more about working the ArchivesSpace guts?  I can understand EAD but obviously 
don’t know the wizardry possible with XML, there’s JSON, python, etc, and I 
would be interested in starting courses with 

Re: [Archivesspace_Users_Group] batch delete dates saga continues

[Galligan, Patrick]

Hey all,

I think a great place to get started learning about Python, APIs, and 
ArchivesSpace would be some of the API tutorials that members of the 
ArchivesSpace community have taught.

Lora Woodford from JHU taught a workshop about 4 months ago and made the 
materials available on Github: 
https://github.com/jhu-archives-and-manuscripts/ASpace_API_Workshop.

Personally, I’ve found that I learn best by doing. So I learned what I did 
about the AS JSON responses by downloading Postman 
(https://www.getpostman.com/) and performing a few API calls against our 
development database. Also, back in 2014, Maureen Callahan and a few other 
archivists ran a blog about dealing with legacy data. They have some posts 
about AS API work. I personally liked this post as a beginner: 
https://icantiemyownshoes.wordpress.com/2014/08/01/a-very-brief-guide-to-deleting-records-with-the-archivesspace-api-from-a-total-tyro/.

This is a great resource for learning python: 
https://automatetheboringstuff.com/.

I’m sure there are a ton of other resources out there, but those are the few 
off the top of my head. I’m willing to jump in and give some more 
recommendations as needed.

-Patrick Galligan

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Margaret Kidd
Sent: Friday, November 10, 2017 5:31 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

I second that last part of Lydia's remarks about where to begin learning more 
about XML, JSON, python, ruby, etc. and applying it to ArchivesSpace. I want to 
learn, but it is overwhelming to know where to begin and my time to devote to 
it is rather limited. Every time I start trying to teach myself I have other 
work priorities that take up all my time and soon forget whatever progress I 
have made.

Thanks,

Margaret




Margaret T. Kidd

Project Archivist, Special Collections & Archives

VCU Libraries | Tompkins-McCaw Library for the Health Sciences

509 N. 12th Street / Box 980582, Richmond, VA 23298-0582

(804) 828-3152
[em_twitter.png][em_fb.png]


[http://identity.vcu.edu/images/photos/vcu_brand_mark_email_sig.jpg]
 
[http://pages.shanti.virginia.edu/Virginia_Heritage/files/2013/01/vhpban.jpg] 



On Fri, Nov 10, 2017 at 12:02 PM, Tang, Lydia 
> wrote:
Mark,
Thank you for identifying my problem!  Just for the sake of technological 
dummies like me, what should I do?  Everything there (besides removing the 
 tags is exactly as it spat out of ArchivesSpace, so I wonder if the 
export allowed the invalid characters?  I also wonder if the importing process 
could be improved within the ArchivesSpace code to search for “aspace_" and not 
batch add it as well as recognize (or not export out in the first place) the 
"Linear Feet" / linear_feet controlled vocabulary?  Ideally, after establishing 
with the database that linear_feet should publish as Linear Feet, I wish it 
would continue to recognize that rule when new stuff is imported in.
I was also meaning poll people on “how do I even get started” with learning 
more about working the ArchivesSpace guts?  I can understand EAD but obviously 
don’t know the wizardry possible with XML, there’s JSON, python, etc, and I 
would be interested in starting courses with Code Academy to learn, but I don’t 
even know where to begin.  Advice appreciated!
Lydia

From: 
>
 on behalf of "Custer, Mark" >
Reply-To: Archivesspace Users Group 
>
Date: Friday, November 10, 2017 at 11:50 AM
To: Archivesspace Users Group 
>
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

Lydia,

In the EAD files that you attached, both have invalid XML characters in them 
(Unicode: 0x14).  Those are easy to remove before re-importing in an XML editor 
like oXygen, but I'm curious how they got into ASpace in the first place?   In 
any event, it's possible that that's what's blocking your imports this time 
around, and if that's the issue, if you just fix on those issues, then the 
ASpace importer won't tell you about the next issue until it runs again.

In any event, I'd also suggest making  the following changes to your XML file 
before re-importing, so perhaps the snag is a good thing for now  :

· ASpace adds "aspace_" to all of the @id values in the EAD file upon