From kate_bowers at harvard.edu Sun Apr 2 11:02:15 2017 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Sun, 2 Apr 2017 15:02:15 +0000 Subject: [Archivesspace_Users_Group] Accruals/related accesions In-Reply-To: References: <29F559819ACA9A4FBF208407D4B63ABB010485F7DC@OC11expo28.exchange.mit.edu> <29F559819ACA9A4FBF208407D4B63ABB010485FFE5@OC11expo28.exchange.mit.edu>, Message-ID: Harvard University took one of the user-defined binaries (check boxes) and labeled it for the purpose of indicating whether or not an accession was a new resource or an accrual to an existing resource. The exact meaning and whether or not to make use of this checkbox is up to each repository. Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 998-5238 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Olivia S Solis Sent: Friday, March 31, 2017 6:07 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Accruals/related accesions Hi Kari, Thanks for the information! Correct me if I'm wrong, but it sounds like you do create a related resource link in each accession to connect it to the appropriate resource record. There are instances where we want to know, for instance, which accession were new in a given time period vs. ones that are not and so that is why having this information would be useful. A user defined field could be a possibility. When we were initially embarking on this ASpace journey, we were resistant to user defined fields, but I've grown warmer to the idea. Thanks again! Olivia On Fri, Mar 31, 2017 at 11:46 AM, Kari R Smith > wrote: Olivia, Would it work to create a User Created data field in the Accession Record to note if the Accession is of TYPE= Accural or TYPE = Accession? That would allow you to run reports on the differences but they would all be related to the Resource record for the overall collection. One thing we did when we were using ATK was to only refer back to the original Accession record when we needed to make the link between the record with certain data (for example, if there is a signed gift agreement) first accession record and the subsequent ones. But we didn?t link all subsequent accession records to themselves. 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 http://libraries.mit.edu/archives/ @karirene69 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Olivia S Solis Sent: Friday, March 31, 2017 10:06 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Accruals/related accesions Hi Kari, Our registrar determines this, but essentially we consider an accession that has the same creator and is the same resource type as an existing collection an accrual. Sometimes this is very obvious. For instance, we are the university archives (University of Texas) and regularly receive records/papers from departments and faculty. So if we have already received an accession from a particular professor, a new accession from him or her would be an accrual. If a professor sends materials to us for the first time, the accession is not an accrual, though any subsequent accessions he/she passes on would be. Most of the time, whether or not something is an accrual is clear to our registrar, but sometimes he has to do a little digging to see if an accession is an addition to an already existing collection. Does that make sense? Thanks, Olivia On Fri, Mar 31, 2017 at 8:32 AM, Kari R Smith > wrote: Hi Olivia, Can you explain more about how you are distinguishing between accessions that are accruals from those that are not? 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 http://libraries.mit.edu/archives/ @karirene69 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Olivia S Solis Sent: Thursday, March 30, 2017 2:06 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Accruals/related accesions Hello all, We at the Briscoe are pretty far along the path to implementing ASpace, but have a number of unresolved issues. One being we are still figuring out how to deal with our accessions that are accruals. The Initially, we had thought to have all accessions in an accrual be related accessions with a sibling relationship. I ran a test with 3 collections: Collection 1, Collection 2, and Collection 3. Steps: 1) Link Collection 1 and Collection 2 as related accessions/siblings. 2) Link Collection 1 and Collection 3 as related accessions/siblings. My assumption was that Collection 2 and Collection 3 would automatically be related as siblings, but this was not the case. Is this behavior a known issue or is there some logic behind this? Am I missing something? I would think that ASpace would consider all the accessions in a daisy-chained series of siblings as siblings of each other. If this is not the case, the maintenance in connecting 20 related accessions/sibling records would be enormous. Nonetheless this led me to decide it might be better to have the first accession in the series of accruals be considered the parent and all the additional accessions be considered related accessions/forms part of the parent/first accrual. I ran another test: 1) Create Collection 4 and spawn an accession from it, Collection 5. 2) Connect the two as related accessions, with Collection 5 designated a child of Collection 4. 3) Spawn a resource from Collection 4, and check related accession. In the spawned resource, only Collection 4 was linked as a related accession in the newly spawned resource. I would have expected Collection 5 to be linked as a related accession in the resource as well. Again, same question. Is this a known issue, or is there some logic behind this? We'd like to indicate all source accessions that are part of the accrual in the related resource records. It would seem like the related accessions should automatically funnel in as related accessions in the resource. How are some of you representing accruals in ArchivesSpace? Have you encountered any problems with your decisions, and did what was the logic of why you decided to go the route that you did? Thanks!! Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Mon Apr 3 11:06:19 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 3 Apr 2017 15:06:19 +0000 Subject: [Archivesspace_Users_Group] interest in participating in an informal registry of ArchivesSpace consultants? Message-ID: Hello everyone, On occasion - and quite a bit recently - we get requests in the program for consulting and other services. Often this is for people who don't want hosting, but need help installing the application, migrating data from a legacy database like Filemaker or a homegrown system, customized training, or custom interface work. While the ArchivesSpace program manages a training program that provides instruction to groups, it can be difficult to keep up with the demand for these kinds of individualized requests, especially when people need onsite services. We'd like to maintain an informal registry of individuals interested in providing consulting services related to ArchivesSpace. The consulting work itself would not be managed by the ArchivesSpace program - consultants and prospective clients would work out any details about the scope of work, deliverables, and compensation amongst themselves. The registry would just be a handy way to gather information about people available to provide services and direct those who are interested to them. If you know of someone, or are interested in this yourself, please let me know. It would be useful to get the following information: * Location * Services * Experience with ArchivesSpace * Best way for prospective clients to get in touch with you and/or see examples of your work (Affiliation with an ArchivesSpace member institution is not required for an individual to be listed in the registry.) For companies and other larger efforts, we do have a Registered Service Provider program which provides additional benefits. Information about the current program is available at http://archivesspace.org/registered-service-providers/why-and-how-to-become-an-rsp/. Feel free to get in touch with me if you have questions or interest in any of these opportunities. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 4144 bytes Desc: image002.jpg URL: From cm77 at nyu.edu Mon Apr 3 15:01:52 2017 From: cm77 at nyu.edu (Carol A Mandel) Date: Mon, 3 Apr 2017 15:01:52 -0400 Subject: [Archivesspace_Users_Group] ArchivesSpace 3rd Quarter Board update Message-ID: <5665c83af3d3a758c317cf5615e2b0de@mail.gmail.com> Dear ArchivesSpace members, I am writing to report on the ArchivesSpace Governance Board 3rd Quarter meeting, which was held in Chicago on March 13th. We were pleased to welcome: ? Heather Heckman, Pennsylvania State Archives, who is serving the remainder of Alston Cobourn?s term as the representative for the small member category. (Alston accepted a new position for an institution that is not in that category, and left the board in December.) ? Bill Mischo, University of Illinois at Urbana-Champaign, who is serving in the place of John Wilkin while John serves as interim provost at UIUC. We reviewed the continued excellent work of the Technical Advisory Council and User Advisory Council--and thanked the members for their dedicated participation. The operations update we received highlighted the good progress by development partner Hudson Molonglo (HM) and the work the program is doing to build policies and infrastructure for further community participation in development. We also discussed the progress on implementation of the Communication and Engagement Plan over the last year and made suggestions for further efforts in this area. The board approved: ? appointments to the Nominating Committee, chaired by Gerald (Jay) Gaidmore, who will announce the committee membership when he sends the call for nominations ? the formation of several subcommittees to update the foundational documents in light of our now well established program and governance, including the ArchivesSpace mission, bylaws and organizational home agreement and ? a resolution in honor of Brad Westbrook?s dedication and founding work on behalf of ArchivesSpace. The text of the resolution is available on the ArchivesSpace website at: http://archivesspace.org/resolution-honoring-bradley-westbrook-founding-archivesspace-program-manager/ We also approved a Fiscal Year 2018 budget. Last year the board approved spending reserve (net asset) funds to drive additional development. As the planned need to expend reserve funds was largely unnecessary this year due to the timing of staffing vacancies (i.e., salary savings were available for the additional development work), the board approved using the reserve funds next year to enable us to capitalize on development momentum and continue to make accelerated progress with the application. As part of our efforts toward greater communication, the ArchivesSpace program will produce an annual report later this year that will include financial information. In closing, I am very happy to report that the ArchivesSpace membership organization is vibrant and is growing at a steady rate. Members are participating in all facets of the program and continue to be its strongest assets and advocates. The Board welcomes your communications and comments to any and all of us, and we extend our thanks to all of you for your continuing support and ongoing contributions to the community we have created. Respectfully, Carol A. Mandel Chair, ArchivesSpace Governance Board Dean, Division of Libraries, New York University -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Apr 4 09:08:52 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 4 Apr 2017 13:08:52 +0000 Subject: [Archivesspace_Users_Group] note for Windows users testing the ArchivesSpace release candidate Message-ID: Hello ArchivesSpace members, In the process of testing, we've discovered an issue with the 2.0.0-RC1 release candidate that affects only Windows users setting it up with a MySQL database. There is some information missing from the setup-database migration script that prevents the migrations from being run on anything but the demo database. This issue does not affect Windows users testing using the embedded database or users with servers on other platforms. (This issue also does not affect users who access ArchivesSpace via a browser on their Windows machine but whose ArchivesSpace server on a different platform.) This issue will be corrected for the release itself, as well as for any future release candidate. If you want to test with Windows and MySQL before then, please add the following to line 5 of the setup-database.bat file found in the scripts directory: set ASPACE_LAUNCHER_BASE=%~dp0%\.. Save the file, and then you should be able to proceed with running the script as usual. If you don't know how to locate this file, or if you aren't sure whether you need to do this, please let me know. Thanks to those testing for bringing this issue to our attention and to our own Laney McGlohon for identifying the solution. Please continue to email me if you encounter issues in the course of testing. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 4144 bytes Desc: image003.jpg URL: From shorowitz at haverford.edu Tue Apr 4 14:33:02 2017 From: shorowitz at haverford.edu (Sarah Horowitz) Date: Tue, 4 Apr 2017 14:33:02 -0400 Subject: [Archivesspace_Users_Group] field for creating an alternate title? Message-ID: Hello everyone, Does anyone create alternate titles for collections? Is there a field you have been using to enter this information? Best, Sarah -- Sarah Horowitz Curator of Rare Books and Manuscripts Head of Quaker & Special Collections Haverford College Libraries Haverford College 370 Lancaster Ave. Haverford, PA 19041 (610) 896-2948 shorowitz at haverford.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Wed Apr 5 10:32:43 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Wed, 5 Apr 2017 09:32:43 -0500 Subject: [Archivesspace_Users_Group] field for creating an alternate title? In-Reply-To: References: Message-ID: Hi Sarah, We were actually wondering about something similar to that too since here at the Briscoe Center, titles of collections sometimes change. Having a "Previous Title" field for resource records would be nice. I believe you would have to use a user-defined field, but someone on this list correct me if I'm wrong. We're going to implement a user-defined field, "Filing Title", just for accessions. This field is in Finding Aid Data in resource records, but there's not a comparable field in accession records and we want to be able to sort records by creator surname sometimes. Not exactly the same as your use case, but thought I'd share nonetheless. Thanks, Olivia On Tue, Apr 4, 2017 at 1:33 PM, Sarah Horowitz wrote: > Hello everyone, > > Does anyone create alternate titles for collections? Is there a field you > have been using to enter this information? > > Best, > Sarah > > -- > Sarah Horowitz > Curator of Rare Books and Manuscripts > Head of Quaker & Special Collections > Haverford College Libraries > Haverford College > 370 Lancaster Ave. > Haverford, PA 19041 > (610) 896-2948 > shorowitz at haverford.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From shorowitz at haverford.edu Wed Apr 5 11:18:46 2017 From: shorowitz at haverford.edu (Sarah Horowitz) Date: Wed, 5 Apr 2017 11:18:46 -0400 Subject: [Archivesspace_Users_Group] field for creating an alternate title? In-Reply-To: References: Message-ID: Thanks Olivia! -- Sarah Horowitz Curator of Rare Books and Manuscripts Head of Quaker & Special Collections Haverford College 370 Lancaster Ave. Haverford, PA 19041 > On Apr 5, 2017, at 10:32 AM, Olivia S Solis wrote: > > Hi Sarah, > > We were actually wondering about something similar to that too since here at the Briscoe Center, titles of collections sometimes change. Having a "Previous Title" field for resource records would be nice. I believe you would have to use a user-defined field, but someone on this list correct me if I'm wrong. > > We're going to implement a user-defined field, "Filing Title", just for accessions. This field is in Finding Aid Data in resource records, but there's not a comparable field in accession records and we want to be able to sort records by creator surname sometimes. Not exactly the same as your use case, but thought I'd share nonetheless. > > Thanks, > Olivia > >> On Tue, Apr 4, 2017 at 1:33 PM, Sarah Horowitz wrote: >> Hello everyone, >> >> Does anyone create alternate titles for collections? Is there a field you have been using to enter this information? >> >> Best, >> Sarah >> >> -- >> Sarah Horowitz >> Curator of Rare Books and Manuscripts >> Head of Quaker & Special Collections >> Haverford College Libraries >> Haverford College >> 370 Lancaster Ave. >> Haverford, PA 19041 >> (610) 896-2948 >> shorowitz at haverford.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > > -- > Olivia Solis, MSIS > Metadata Coordinator > Dolph Briscoe Center for American History > The University of Texas at Austin > 2300 Red River St. Stop D1100 > Austin TX, 78712-1426 > (512) 232-8013 > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From hawkpf at miamioh.edu Wed Apr 5 15:47:29 2017 From: hawkpf at miamioh.edu (Hawk, Patrick) Date: Wed, 5 Apr 2017 15:47:29 -0400 Subject: [Archivesspace_Users_Group] Failure in periodic indexer worker thread In-Reply-To: References: <10B09366-1478-49A6-B1C1-FFBC15BB547D@eservices.virginia.edu> <3209f21eab7c4ce1aba859edf7f38d60@EX01.ads.nmu.edu> <3BF93CDE-1B84-48AC-A9F7-1F442B0CA406@eservices.virginia.edu> <8F4DD791-A2D3-4DB4-9507-37296B1C13EA@eservices.virginia.edu> Message-ID: I wanted to respond to this thread on what I had to do to complete the migration. I decided to remove all of the barcode_1 that were duplicates and make them null. I did not want to lose the information so I placed the barcodes in the notes section of the housed_at_rlshp table. I hid the database name for security reasons and replaced it with databasename. update databasename.housed_at_rlshp a, databasename.container b set a.note = CONCAT(a.note, ', ', b.barcode_1) where a.container_id = b.id and b.barcode_1 is not null; update databasename.housed_at_rlshp a, databasename.container b set a.note = b.barcode_1 where a.container_id = b.id and b.barcode_1 is not null and a.note is null; update databasename.housed_at_rlshp a, databasename.container b set b.barcode_1 = null where a.container_id = b.id and b.barcode_1 = a.note and b.barcode_1 is not null and a.note is not null; Thanks for the feedback everyone! On Wed, Mar 29, 2017 at 8:31 PM, James Bullen wrote: > > Hi Patrick, > > This is a bit confusing because there are currently two container tables: > ?container? and ?top_container?. > > ?container? is the old container table - ie from before the container > management plugin was merged in. > ?top_container? is the new container table - ie it was introduced as part > of the container management merge. > > The ?container? table should really have been dropped when the container > management plugin was merged in, but that can?t be done yet because a bunch > of code still depends on it, and there?s some cunning mapping that goes on > between the two tables behind the scenes. It is on our list of priorities > for the next major release (currently scheduled for June) to resolve this > and a few other issues surrounding the container management merge. > > So, to your question about barcodes: > container.barcode does not have a unique constraint. > top_container.barcode must be unique within a repository. > > In the old container model, container records are nested sub-records, so > many container records might refer to the same physical box. This means > that is was not possible to have barcodes be unique. In the new container > management model a top_container record represents a physical box, so it is > possible to enforce unique barcodes in the database. > > Hope that helps. > > > Cheers, > James > > > On Mar 30, 2017, at 5:27 AM, Majewski, Steven Dennis (sdm7g) < > sdm7g at eservices.virginia.edu> wrote: > > PS: There was also Mark Cooper?s container migration notes: > https://gist.github.com/mark-cooper/96892ab8734cf96a5a6ab0268107ab45 > > And some Yale screencasts: > http://guides.library.yale.edu/archivesspace/ASpaceContainerManagement > > ? Steve. > > > On Mar 29, 2017, at 2:21 PM, Majewski, Steven Dennis (sdm7g) < > sdm7g at eservices.virginia.edu> wrote: > > > On Mar 29, 2017, at 1:26 PM, Hawk, Patrick wrote: > > Steve, > > I'm attaching a screen capture. The barcode_1 field needs to be unique in > the table container? > > > > That?s my understanding, although I?m not certain if they have to be > globally unique or just unique within that resource. ( I expect the > intention is for them to be globally unique, but I?m not sure if they > actually check beyond the current resource. ) I?m not sure, but I don?t > think a barcode is required, so another option may be to just delete those > barcodes. Or, as I initially suggested, append ?box 1?, ?box 2? , etc. to > your existing barcodes to make them unique. > > > I believe there was some discussion relating to these issues in the 1.5.0 > release webinar, probably in Noah?s talks and notes: > > http://archivesspace.org/recording-and-slides-for-v1-5-0-release-webinar/ > > If you haven?t already, you should check it out, as it?s the easiest intro > the what?s involved in the migration. ( I don?t think the upgrading docs in > the distribution explain the terminology and background sufficiently. ) > > > ? Steve. > > > On Thu, Mar 16, 2017 at 1:10 PM, Majewski, Steven Dennis (sdm7g) < > sdm7g at eservices.virginia.edu> wrote: > >> >> I interpret that error message as saying that you are trying to assign >> the same barcode ( "Miami University Archives (Western College for Women >> Collection)? ) to ?box 1? and ?box 2? (type + indicator). Barcodes must be >> unique. A collection name is not likely to be unique if there are more than >> one containers. Typically, these are machine scannable barcode numbers. If >> you really want to use the collection name here, you could maybe append the >> box numbers to the ends of both, making them unique. >> >> >> ? Steve. >> >> >> On Mar 16, 2017, at 12:10 PM, Hawk, Patrick wrote: >> >> John, >> Do you know which two accessions you had to modify? >> >> Also, this is what I see in archivesspace/logs/archivesspace.out >> >> <:ValidationException: {:errors=>{"indicator_1"=>["Mismatch when mapping >> between indicator and indicator_1"]}, :object_context=>{:top_container=>#> @values={:id=>2, :repo_id=>2, :lock_version=>0, :json_schema_version=>1, >> :barcode=>"Miami University Archives (Western College for Women >> Collection)", :ils_holding_id=>nil, :ils_item_id=>nil, >> :exported_to_ils=>nil, :indicator=>"1", :created_by=>"XXXX", >> :last_modified_by=>"XXXX", :create_time=>2017-03-15 20:01:48 UTC, >> :system_mtime=>2017-03-15 20:01:48 UTC, :user_mtime=>2017-03-15 20:01:48 >> UTC, :type_id=>318}>, :aspace_container=>{"lock_version"=>0, >> "indicator_1"=>"2", "barcode_1"=>"Miami University Archives (Western >> College for Women Collection)", "container_extent"=>"1.00", >> "created_by"=>"XXXX", "last_modified_by"=>"XXXX", >> "create_time"=>"2016-02-16T15:42:01Z", "system_mtime"=>"2016-11-15T18:16:09Z", >> "user_mtime"=>"2016-02-16T15:42:01Z", "type_1"=>"box", >> "container_extent_type"=>"Boxes", "jsonmodel_type"=>"container", >> "container_locations"=>[{"status"=>"current", >> "start_date"=>"1999-12-31", "system_mtime"=>2016-02-16 15:42:01 UTC, >> "user_mtime"=>2016-02-16 15:42:01 UTC, "ref"=>"/locations/8584"}], >> "type_id"=>318}}}> >> >> >> >> On Tue, Mar 14, 2017 at 3:40 PM, Hambleton, John S >> wrote: >> >>> Hello! >>> >>> >>> >>> That thread below was us, Northern Michigan University. >>> >>> Looking in the container conversion log, was this error: >>> >>> >>> >>> Error: >>> >>> JSONModel::ValidationException >>> >>> >>> >>> Message: >>> >>> indicator_1 -- Mismatch when mapping between indicator and indicator_1 >>> >>> >>> >>> James Bullen took a look at our log and determined that there was a >>> barcode >>> >>> uniqueness problem between two accessions. So we cleaned that up and >>> sure enough, >>> >>> that was it. We re-ran the conversion and the indexer did not have any >>> problems. >>> >>> >>> >>> Hope this helps you. >>> >>> >>> >>> John H >>> >>> NMU >>> >>> >>> >>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: >>> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Hawk, >>> Patrick >>> *Sent:* Tuesday, March 14, 2017 3:27 PM >>> *To:* Archivesspace Users Group >> alists.lyrasis.org> >>> *Subject:* Re: [Archivesspace_Users_Group] Failure in periodic indexer >>> worker thread >>> >>> >>> >>> Steve, >>> The url you linked would be the same issue, so yes the indexer tries to >>> index the same items over and over... I'll have to inspect the records to >>> see what is causing the migration to fail. >>> >>> >>> >>> On Tue, Mar 14, 2017 at 3:13 PM, Majewski, Steven Dennis (sdm7g) < >>> sdm7g at eservices.virginia.edu> wrote: >>> >>> >>> >>> Check for errors in the container conversion batch job log files. >>> >>> >>> >>> Does the indexer appear to keep trying to reindex the same records over >>> and over ? >>> >>> >>> >>> See previous thread: >>> >>> http://lyralists.lyrasis.org/pipermail/archivesspace_users_g >>> roup/2017-January/004370.html >>> >>> >>> >>> ? Steve Majewski >>> >>> >>> >>> >>> >>> >>> >>> On Mar 14, 2017, at 2:45 PM, Hawk, Patrick wrote: >>> >>> >>> >>> Hello, >>> >>> I'm trying to upgrade Archivesspace from 1.4.2 to 1.5.3 but I'm having >>> issues getting my content to fully load. I followed the instructions here: >>> http://archivesspace.github.io/archivesspace/user/ >>> upgrading-to-a-new-release-of-archivesspace/. I removed the directory >>> /archivesspace/data/indexter_state and /archivesspace/data/solr_index/index >>> as the directions stated I should do when upgrading to 1.5.0. I also ran >>> the setup-database.sh without issue. >>> >>> >>> >>> However, I receive the following error: Failure in periodic indexer >>> worker thread: {"error":"undefined method `related_records' for >>> nil:NilClass"} in the archivesspace.out file. At this point the logs >>> suggest that all items have been re-indexed but my content does not fully >>> load. Any suggestions? >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> >>> >>> -- >>> >>> Patrick Hawk >>> >>> King Library Systems >>> >>> King Library Room 314 >>> >>> 513-529-6122 <(513)%20529-6122> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >> >> >> -- >> >> Patrick Hawk >> >> >> King Library Systems >> >> King Library Room 314 >> >> 513-529-6122 <(513)%20529-6122> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > > Patrick Hawk > > > King Library Systems > > King Library Room 314 > > 513-529-6122 <(513)%20529-6122> > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:58dbfcac43573521512206! > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:58dbfcac43573521512206! > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Patrick Hawk King Library Systems King Library Room 314 513-529-6122 -------------- next part -------------- An HTML attachment was scrubbed... URL: From hawkpf at miamioh.edu Thu Apr 6 09:54:17 2017 From: hawkpf at miamioh.edu (Hawk, Patrick) Date: Thu, 6 Apr 2017 09:54:17 -0400 Subject: [Archivesspace_Users_Group] Failure in periodic indexer worker thread In-Reply-To: References: <10B09366-1478-49A6-B1C1-FFBC15BB547D@eservices.virginia.edu> <3209f21eab7c4ce1aba859edf7f38d60@EX01.ads.nmu.edu> <3BF93CDE-1B84-48AC-A9F7-1F442B0CA406@eservices.virginia.edu> <8F4DD791-A2D3-4DB4-9507-37296B1C13EA@eservices.virginia.edu> Message-ID: I wanted to respond to this thread on what I had to do to complete the migration. I decided to remove all of the barcode_1 that were duplicates and make them null. I did not want to lose the information so I placed the barcodes in the notes section of the housed_at_rlshp table. I hid the database name for security reasons and replaced it with databasename. update databasename.housed_at_rlshp a, databasename.container b set a.note = CONCAT(a.note, ', ', b.barcode_1) where a.container_id = b.id and b.barcode_1 is not null; update databasename.housed_at_rlshp a, databasename.container b set a.note = b.barcode_1 where a.container_id = b.id and b.barcode_1 is not null and a.note is null; update databasename.housed_at_rlshp a, databasename.container b set b.barcode_1 = null where a.container_id = b.id and b.barcode_1 = a.note and b.barcode_1 is not null and a.note is not null; Thanks for the feedback everyone! Sorry if there's a duplicate, but I have not seen this posted to the message boards so I posted a second time. On Wed, Mar 29, 2017 at 8:31 PM, James Bullen wrote: > > Hi Patrick, > > This is a bit confusing because there are currently two container tables: > ?container? and ?top_container?. > > ?container? is the old container table - ie from before the container > management plugin was merged in. > ?top_container? is the new container table - ie it was introduced as part > of the container management merge. > > The ?container? table should really have been dropped when the container > management plugin was merged in, but that can?t be done yet because a bunch > of code still depends on it, and there?s some cunning mapping that goes on > between the two tables behind the scenes. It is on our list of priorities > for the next major release (currently scheduled for June) to resolve this > and a few other issues surrounding the container management merge. > > So, to your question about barcodes: > container.barcode does not have a unique constraint. > top_container.barcode must be unique within a repository. > > In the old container model, container records are nested sub-records, so > many container records might refer to the same physical box. This means > that is was not possible to have barcodes be unique. In the new container > management model a top_container record represents a physical box, so it is > possible to enforce unique barcodes in the database. > > Hope that helps. > > > Cheers, > James > > > On Mar 30, 2017, at 5:27 AM, Majewski, Steven Dennis (sdm7g) < > sdm7g at eservices.virginia.edu> wrote: > > PS: There was also Mark Cooper?s container migration notes: > https://gist.github.com/mark-cooper/96892ab8734cf96a5a6ab0268107ab45 > > And some Yale screencasts: > http://guides.library.yale.edu/archivesspace/ASpaceContainerManagement > > ? Steve. > > > On Mar 29, 2017, at 2:21 PM, Majewski, Steven Dennis (sdm7g) < > sdm7g at eservices.virginia.edu> wrote: > > > On Mar 29, 2017, at 1:26 PM, Hawk, Patrick wrote: > > Steve, > > I'm attaching a screen capture. The barcode_1 field needs to be unique in > the table container? > > > > That?s my understanding, although I?m not certain if they have to be > globally unique or just unique within that resource. ( I expect the > intention is for them to be globally unique, but I?m not sure if they > actually check beyond the current resource. ) I?m not sure, but I don?t > think a barcode is required, so another option may be to just delete those > barcodes. Or, as I initially suggested, append ?box 1?, ?box 2? , etc. to > your existing barcodes to make them unique. > > > I believe there was some discussion relating to these issues in the 1.5.0 > release webinar, probably in Noah?s talks and notes: > > http://archivesspace.org/recording-and-slides-for-v1-5-0-release-webinar/ > > If you haven?t already, you should check it out, as it?s the easiest intro > the what?s involved in the migration. ( I don?t think the upgrading docs in > the distribution explain the terminology and background sufficiently. ) > > > ? Steve. > > > On Thu, Mar 16, 2017 at 1:10 PM, Majewski, Steven Dennis (sdm7g) < > sdm7g at eservices.virginia.edu> wrote: > >> >> I interpret that error message as saying that you are trying to assign >> the same barcode ( "Miami University Archives (Western College for Women >> Collection)? ) to ?box 1? and ?box 2? (type + indicator). Barcodes must be >> unique. A collection name is not likely to be unique if there are more than >> one containers. Typically, these are machine scannable barcode numbers. If >> you really want to use the collection name here, you could maybe append the >> box numbers to the ends of both, making them unique. >> >> >> ? Steve. >> >> >> On Mar 16, 2017, at 12:10 PM, Hawk, Patrick wrote: >> >> John, >> Do you know which two accessions you had to modify? >> >> Also, this is what I see in archivesspace/logs/archivesspace.out >> >> <:ValidationException: {:errors=>{"indicator_1"=>["Mismatch when mapping >> between indicator and indicator_1"]}, :object_context=>{:top_container=>#> @values={:id=>2, :repo_id=>2, :lock_version=>0, :json_schema_version=>1, >> :barcode=>"Miami University Archives (Western College for Women >> Collection)", :ils_holding_id=>nil, :ils_item_id=>nil, >> :exported_to_ils=>nil, :indicator=>"1", :created_by=>"XXXX", >> :last_modified_by=>"XXXX", :create_time=>2017-03-15 20:01:48 UTC, >> :system_mtime=>2017-03-15 20:01:48 UTC, :user_mtime=>2017-03-15 20:01:48 >> UTC, :type_id=>318}>, :aspace_container=>{"lock_version"=>0, >> "indicator_1"=>"2", "barcode_1"=>"Miami University Archives (Western >> College for Women Collection)", "container_extent"=>"1.00", >> "created_by"=>"XXXX", "last_modified_by"=>"XXXX", >> "create_time"=>"2016-02-16T15:42:01Z", "system_mtime"=>"2016-11-15T18:16:09Z", >> "user_mtime"=>"2016-02-16T15:42:01Z", "type_1"=>"box", >> "container_extent_type"=>"Boxes", "jsonmodel_type"=>"container", >> "container_locations"=>[{"status"=>"current", >> "start_date"=>"1999-12-31", "system_mtime"=>2016-02-16 15:42:01 UTC, >> "user_mtime"=>2016-02-16 15:42:01 UTC, "ref"=>"/locations/8584"}], >> "type_id"=>318}}}> >> >> >> >> On Tue, Mar 14, 2017 at 3:40 PM, Hambleton, John S >> wrote: >> >>> Hello! >>> >>> >>> >>> That thread below was us, Northern Michigan University. >>> >>> Looking in the container conversion log, was this error: >>> >>> >>> >>> Error: >>> >>> JSONModel::ValidationException >>> >>> >>> >>> Message: >>> >>> indicator_1 -- Mismatch when mapping between indicator and indicator_1 >>> >>> >>> >>> James Bullen took a look at our log and determined that there was a >>> barcode >>> >>> uniqueness problem between two accessions. So we cleaned that up and >>> sure enough, >>> >>> that was it. We re-ran the conversion and the indexer did not have any >>> problems. >>> >>> >>> >>> Hope this helps you. >>> >>> >>> >>> John H >>> >>> NMU >>> >>> >>> >>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: >>> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Hawk, >>> Patrick >>> *Sent:* Tuesday, March 14, 2017 3:27 PM >>> *To:* Archivesspace Users Group >> alists.lyrasis.org> >>> *Subject:* Re: [Archivesspace_Users_Group] Failure in periodic indexer >>> worker thread >>> >>> >>> >>> Steve, >>> The url you linked would be the same issue, so yes the indexer tries to >>> index the same items over and over... I'll have to inspect the records to >>> see what is causing the migration to fail. >>> >>> >>> >>> On Tue, Mar 14, 2017 at 3:13 PM, Majewski, Steven Dennis (sdm7g) < >>> sdm7g at eservices.virginia.edu> wrote: >>> >>> >>> >>> Check for errors in the container conversion batch job log files. >>> >>> >>> >>> Does the indexer appear to keep trying to reindex the same records over >>> and over ? >>> >>> >>> >>> See previous thread: >>> >>> http://lyralists.lyrasis.org/pipermail/archivesspace_users_g >>> roup/2017-January/004370.html >>> >>> >>> >>> ? Steve Majewski >>> >>> >>> >>> >>> >>> >>> >>> On Mar 14, 2017, at 2:45 PM, Hawk, Patrick wrote: >>> >>> >>> >>> Hello, >>> >>> I'm trying to upgrade Archivesspace from 1.4.2 to 1.5.3 but I'm having >>> issues getting my content to fully load. I followed the instructions here: >>> http://archivesspace.github.io/archivesspace/user/ >>> upgrading-to-a-new-release-of-archivesspace/. I removed the directory >>> /archivesspace/data/indexter_state and /archivesspace/data/solr_index/index >>> as the directions stated I should do when upgrading to 1.5.0. I also ran >>> the setup-database.sh without issue. >>> >>> >>> >>> However, I receive the following error: Failure in periodic indexer >>> worker thread: {"error":"undefined method `related_records' for >>> nil:NilClass"} in the archivesspace.out file. At this point the logs >>> suggest that all items have been re-indexed but my content does not fully >>> load. Any suggestions? >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> >>> >>> -- >>> >>> Patrick Hawk >>> >>> King Library Systems >>> >>> King Library Room 314 >>> >>> 513-529-6122 <(513)%20529-6122> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >> >> >> -- >> >> Patrick Hawk >> >> >> King Library Systems >> >> King Library Room 314 >> >> 513-529-6122 <(513)%20529-6122> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > > Patrick Hawk > > > King Library Systems > > King Library Room 314 > > 513-529-6122 <(513)%20529-6122> > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:58dbfcac43573521512206! > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:58dbfcac43573521512206! > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Patrick Hawk King Library Systems King Library Room 314 513-529-6122 -------------- next part -------------- An HTML attachment was scrubbed... URL: From francis.lapka at yale.edu Thu Apr 6 16:23:24 2017 From: francis.lapka at yale.edu (Lapka, Francis) Date: Thu, 6 Apr 2017 20:23:24 +0000 Subject: [Archivesspace_Users_Group] LCNAF plugin Message-ID: As part of a larger project concerning agent and subject records in ArchivesSpace, a group at Yale has drafted changes we'd like to see in the LCNAF plugin (to be coded by a vendor for use at Yale). The spec is outlined here: https://drive.google.com/open?id=1_Jt0_5_9uuu-YexjfIdzTQEuJo2GjQ88no8WxHBXPlI There are three tabs. Text in red indicates changes to existing performance of the plugin (except for the third tab - where we propose an entirely new mapping for lcgft). Some of what we propose may not be universally desired (e.g., using the LC authority URI as AS AuthorityID). Other changes probably ought to be incorporated in the LCNAF plugin for all (e.g., don't create separate AS subject *records* for each variant form in an LCSH record). We welcome your corrections, suggestions, or other thoughts. Thanks, Francis Francis Lapka * Catalog Librarian Dept. of Rare Books and Manuscripts Yale Center for British Art 203.432.9672 * francis.lapka at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From laddmm at miamioh.edu Fri Apr 7 08:29:46 2017 From: laddmm at miamioh.edu (Ladd, Marcus) Date: Fri, 7 Apr 2017 08:29:46 -0400 Subject: [Archivesspace_Users_Group] Top Container Issues Message-ID: We have just recently upgraded to the most recent version, and we're having problems with how Top Container has merged both Container information and the Location information. For example, our some of our materials move between locations when they are on loan, and with the new structure this would mean we have to recreate the Top Container information every time, rather than just changing the location. Has anyone else encountered similar problems and found a way to make the new structure work? Also, is there specific documentation in one of the updates that explains the Top Container field and what it replaces? thanks, Marcus -------- *Marcus Ladd* Special Collections Digital Librarian Miami University, Oxford, OH -------------- next part -------------- An HTML attachment was scrubbed... URL: From gpgaidmore at wm.edu Fri Apr 7 19:53:45 2017 From: gpgaidmore at wm.edu (Gaidmore, Gerald) Date: Fri, 7 Apr 2017 23:53:45 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace User Advisory Council Message-ID: The ArchivesSpace Governance Board is seeking nominations to fill up to 4 vacancies on the ArchivesSpace User Advisory Council (UAC). Nominees should be presently employed at an ArchivesSpace member institution in the Large, Medium, or Very Small levels (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). Nominations may be made only by ArchivesSpace Member Representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member Representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities projected for UAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 28. The Nominations Committee will review all nominations and recommend appointments to the Governance Board for approval. UAC (http://archivesspace.org/governance-board-and-councils/#UAC) is a critical part of the ArchivesSpace community, serving as a communication conduit between ArchivesSpace governance groups and ArchivesSpace users. It is also the group that implements and contributes to ArchivesSpace user services. Some of the activities UAC is currently engaged in are: * soliciting, suggesting, and gathering requirements for enhancements to the ArchivesSpace application; * developing functional specifications for reports with the application; * reviewing enhancements and priorities, and testing in collaboration with the Technical Advisory Council; * maintaining and updating user documentation, as needed, of the ArchivesSpace application. Sub-teams will be established within UAC to address the areas identified above, as well as other activities identified subsequently. Nominees will be appointed to UAC according to their ability to participate in and lead some of the activities mentioned above. To nominate a candidate for the ArchivesSpace User Advisory Council, please identify the person and her/his organization in the form below, indicate the areas of activity to which the nominee is prepared to contribute. Again, self-nominations are also welcome. Return the completed form via email to ArchivesSpace Program Manager, Christine Di Bella (christine.dibella at lyrasis.org), who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 28. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service will be July 1, 2017-June 30, 2019. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2019-June 30, 2021. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, Jay Gaidmore The College of William & Mary Chair, and Governance Board member On behalf of Nominating Committee members: Gordon Daines, Brigham Young University, Chair of User Advisory Council Sally Vermaaten, Gates Archives, Chair of Technical Advisory Council Johna Von Behrens, University of Louisiana Lafayette, representing Very Large membership level Cyndi Shein, UNLV, representing Large membership level Mary Saffell, Texas Christian University, representing Medium membership level Julia Novakovic, The Strong National Museum of Play, representing Small membership level Annie Tummino, SUNY Maritime, representing Very Small membership level Christine Di Bella, ArchivesSpace Program Manager, ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___New features, functional or technical specifications ___ Usability and quality assurance testing ___User/Help support ___Documentation -------------- next part -------------- An HTML attachment was scrubbed... URL: From gpgaidmore at wm.edu Fri Apr 7 19:53:54 2017 From: gpgaidmore at wm.edu (Gaidmore, Gerald) Date: Fri, 7 Apr 2017 23:53:54 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Technical Advisory Council Message-ID: <0dc6c82b69fb44889c8616b4a490fb5d@EXMBX02.campus.wm.edu> The ArchivesSpace Governance Board is looking for nominations to fill up to 7 vacancies on the ArchivesSpace Technical Advisory Council (TAC). Nominees should be presently employed at an ArchivesSpace member institution in the Very Large, Large, Medium, Small, or Very Small levels (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). They may also be employees of a current Registered Service Provider (see: http://archivesspace.org/registered-service-providers/current-rsps/). Nominations may be made only by ArchivesSpace Member Representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities assigned to TAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 28. The Nominating Committee will review all nominations and recommend appointments to the Governance Board for approval. TAC (http://archivesspace.org/governance-board-and-councils/#TAC) is a critical part of the ArchivesSpace community, having responsibility for providing technical guidance to individuals or organizations contributing to application development, to the User Advisory Council, and to the ArchivesSpace Governance Board. TAC's current activities include: * developing a community of code committers, including helping to establish guidelines for contributing code and reviewing contributions, * reviewing enhancements and priorities, and testing in collaboration with the User Advisory Council, * providing support for migrating data to ArchivesSpace from other systems and support for importing and exporting data such as EAD, MARCXML, CSV * documenting and assisting with resolving bugs identified in the application, * identifying integration points for ArchivesSpace with other systems (e.g. digital asset management systems, patron and request management systems, etc.), creating resources to assist the community with integration work and, for specific integrations, developing technical requirements, and * updating technical documentation. Sub-teams will be established within TAC to address the areas identified above, as well other activity areas identified subsequently. Nominees must have sufficient knowledge of application development methods, architectures and coding practices to participate in and lead some of the identified activities. Nominees with experience in open source projects, developing web applications (particularly using Ruby on Rails and Sinatra), software testing, or interest in those areas, are especially welcome. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service for these appointments will be July 1, 2017-June 30, 2019. We expect to make up to 7 appointments, and each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2019-June 30, 2021. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicating the areas of activity to which the nominee is prepared to contribute. Again, self-nominations are also welcome. Return the completed form via email to the ArchivesSpace Program Manager, Christine Di Bella (christine.dibella at lyrasis.org), who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 28. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, Jay Gaidmore The College of William & Mary Chair, and Governance Board member On behalf of Nominating Committee members: Gordon Daines, Brigham Young University, Chair of User Advisory Council Sally Vermaaten, Gates Archives, Chair of Technical Advisory Council Johna Von Behrens, University of Louisiana Lafayette, representing Very Large membership level Cyndi Shein, UNLV, representing Large membership level Mary Saffell, Texas Christian University, representing Medium membership level Julia Novakovic, The Strong National Museum of Play, representing Small membership level Annie Tummino, SUNY Maritime, representing Very Small membership level Christine Di Bella, ArchivesSpace Program Manager, ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Managing/endorsing/eliciting code contributions ___Application testing ___Migration issues, including import/exports and API design and implementation ___Bug fixes ___Program architecture and integrations with other software ___Technical documentation -------------- next part -------------- An HTML attachment was scrubbed... URL: From gpgaidmore at wm.edu Fri Apr 7 19:54:02 2017 From: gpgaidmore at wm.edu (Gaidmore, Gerald) Date: Fri, 7 Apr 2017 23:54:02 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Governance Board Message-ID: As chair of the 2017/18 ArchivesSpace Nominating Committee, I am writing to seek your nominations of candidates to stand for election for the ArchivesSpace Governance Board (http://archivesspace.org/governance-board-and-councils/#GovernanceBoard) - representing the Large, Medium, and Very Small membership levels. Member engagement is critical to the success of ArchivesSpace, and the Board relies upon your recommendations for strong candidates. Even if you represent a different category of membership, please consider colleagues you know at other institutions. Only ArchivesSpace Member Representatives may submit nominations. All other staff of ArchivesSpace member organizations must submit nominations through their Member Representative. All Member Representatives are strongly encouraged to consult with all interested colleagues within their organization to solicit recommendations for nominees. Self-nominations are also welcome if you represent a Large, Medium, or Very Small member institution. To submit nominations, send the name and institutional affiliation for each person, and indicate whether or not you have contacted the nominee. A member of the Nominating Committee will follow up with the nominee accordingly to confirm their interest. Self-nominees can simply indicate their interest. Nominees who confirm their interest in standing for election will be requested to supply a formal candidate statement outlining their qualifications for serving on the Governance Board. Nominations must be received by 9:00 p.m. EDT Friday, April 28. They should be sent to ArchivesSpace Program Manager Christine Di Bella (christine.dibella at lyrasis.org), who will collect nominations on behalf of the Nominating Committee. The Nominating Committee will review all nominations and confirm a slate of nominees with the current Governance Board. An election ballot will be circulated to member institutions in mid-May. The current incumbents at the Large and Very Small membership levels are eligible for re-election as representatives to the Governance Board. The current incumbent at the Medium membership level is no longer eligible for appointment. The terms for their successors will be July 1, 2017-June 30, 2019. Each newly elected member representative will be eligible to run for a second term, July 1, 2019-June 30, 2021. Nominees must be currently employed by an ArchivesSpace member organization in either the Large, Medium, and Very Small member levels (see the member lists at: http://archivesspace.org/community/whos-using-archivesspace/). Nominees should have administrative and fiscal oversight experience, characteristics typical of director or associate director level staff. The Governance Board is charged with providing oversight for the ArchivesSpace application and community, including fiscal oversight, the approval of development priorities, and oversight of the Technical and User Advisory councils. To meet the needs of a broad and diverse membership in a balanced and equitable way, the Governance Board is composed of twelve members, including: 9 voting members: 5 elected members, one from each of the five membership categories; 3 standing members, one representing each of the three original project partners (New York University, UC San Diego, and the University of Illinois, Urbana-Champaign); and 1 member representing the LYRASIS management team. 3 ex officio members: ArchivesSpace Program Manager, LYRASIS Director of Collection Services and Community Supported Software, and 1 member of the LYRASIS Board of Directors. Please feel free to contact me or any member of our Nominating Committee with any questions. Again, nominations should be sent to ArchivesSpace Program Manager Christine Di Bella (christine.dibella at lyrasis.org). All nominations must be received by Friday, April 28. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, Jay Gaidmore The College of William & Mary Chair, and Governance Board member On behalf of Nominating Committee members: Gordon Daines, Brigham Young University, Chair of User Advisory Council Sally Vermaaten, Gates Archives, Chair of Technical Advisory Council Johna Von Behrens, University of Louisiana Lafayette, representing Very Large membership level Cyndi Shein, UNLV, representing Large membership level Mary Saffell, Texas Christian University, representing Medium membership level Julia Novakovic, The Strong National Museum of Play, representing Small membership level Annie Tummino, SUNY Maritime, representing Very Small membership level Christine Di Bella, ArchivesSpace Program Manager, ex officio -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Mon Apr 10 09:35:52 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 10 Apr 2017 13:35:52 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - April 2017 Message-ID: [ASpaceOrgHome.jpg] April 2017 Update Development We are pleased to announce that a release candidate - v2.0.0-RC1 (https://github.com/archivesspace/archivesspace/releases/tag/v2.0.0-RC1) - is available for download and testing purposes. Version 2.0.0 of ArchivesSpace will be a major release, with many changes to the underlying technologies of the application as well as improved functionality in some key areas. Summary information about these changes is available at the release notes accompanying the release candidate. The changes include upgrading to Rails 5, better performance for background jobs and larger databases, a new way to reorder components in resources and digital objects, and remediation of issues with reports. By default, this file will use the current public interface for ArchivesSpace. This release candidate features substantial work from our development partner, Hudson Molonglo (HM), as well as contributions from community members. Public User Interface (PUI) The release notes indicate that the new public interface beta is available if you/your system administrator make a change to an environmental variable. Instructions for doing so are in the release notes. Because the new public interface is a beta (i.e. not ready for production use) and is still being actively worked on in order to get as much of the requested functionality into it as possible by the June full release, you should not change this setting on your production server, even if you are not currently using the public interface. This is essentially a sneak preview of major functionality and we look forward to your feedback. The beta includes many of the most complex elements of this work, and more functionality, including the ability to print records to PDF, will be included in the June release. The new public interface reflects tireless work in this area led by Mark Custer of Yale University, and features input from our member working group participants and web firm Cherry Hill Company (who worked with the group in 2015), as well as development by HM (largely funded by Yale) and Harvard developers. Details on this work, including the wireframes and functionality that are guiding the development phase of this work, are available at https://archivesspace.atlassian.net/wiki/display/ADC/Public+Interface+Enhancement+Project. Testing and Feedback We are collecting feedback on the release candidate until April 12. Please email Program Manager Christine Di Bella (christine.dibella at lyrasis.org) if you encounter any issues. We will determine an exact release date for 2.0.0 when we are confident in the testing results, but hope that it will follow on quickly from the feedback deadline. Please let us know if you experience any problems. If you use this release candidate with your own data, please note that a full index is required. Also, please note that running reports requires a MySQL database backend. You will not be able to run reports with the embedded database. Resolution Honoring Bradley Westbrook, Founding ArchivesSpace Program Manager The ArchivesSpace Governance Board recently approved a resolution honoring Bradley Westbrook, ArchivesSpace's founding program manager and longtime leader in archival information management. The text of the resolution was presented to him in February, and is as follows: Whereas, for more than a decade Bradley Westbrook has been a visionary leader in meeting the needs of the archival community for archival management software, including his central role in the genesis of the Archivists Toolkit, which later merged into ArchivesSpace; Whereas, Bradley Westbrook has been a tireless major contributor to the development of ArchivesSpace from its inception; Whereas, Bradley Westbrook served as the founding Program Manager of the new ArchivesSpace membership organization, uniting the archival community in a common enterprise to sustain, enhance and help each other to use the ArchivesSpace software; BE IT RESOLVED, that the ArchivesSpace Board of Governors expresses its deepest gratitude and appreciation to Bradley Westbrook and commends him for his singular vision, leadership and dedication in the creation of ArchivesSpace and its sustaining membership organization. We thank Brad for all his many contributions to our community and for his singular vision in making ArchivesSpace a reality. We're Hiring! LYRASIS is hiring for an ArchivesSpace Community Engagement Coordinator. Reporting to the Program Manager, the Community Engagement Coordinator will be on the frontlines of the program, helping ArchivesSpace users get as much as possible out of the application and bringing our community together. The position will be especially focused on user support, outreach, communications, training, user documentation, and testing. The full listing is available on the LYRASIS website at https://www.lyrasis.org/job/Pages/LYRASIS-Positions.aspx. Those interested in the position should apply by submitting a cover letter and resume to human.resources at lyrasis.org. Priority consideration will be given to applications received by April 21. Nominations for ArchivesSpace Governance Groups Calls for nominations for openings on the ArchivesSpace Governance Board, User Advisory Council (UAC), and Technical Advisory Council (TAC) with terms beginning in July 2017 were recently announced. ArchivesSpace members from institutions in the Large, Medium, and Very Small categories are eligible for consideration for the Governance Board election, and members from institutions at all levels are eligible for openings on the UAC and TAC. Representatives of Registered Service Providers are also eligible for openings on the TAC. More information on each call is available at: Governance Board: http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2017-April/004664.html User Advisory Council: http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2017-April/004662.html Technical Advisory Council: http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2017-April/004663.html Volunteers are the lifeblood of ArchivesSpace and we heartily thank all who serve and consider serving. Please submit nominations to Program Manager Christine Di Bella (christine.dibella at lyrasis.org) on behalf of the Nominating Committee by Friday, April 28, 9:00 p.m. EDT. ArchivesSpace Member Forum 2017 The 2017 ArchivesSpace Member Forum will be held on Tuesday, July 25, at Portland State University. This event is open to all staff from ArchivesSpace member institutions and will feature a variety of opportunities to learn and share about all things ArchivesSpace. A call for speakers will be going out soon. Follow along, or make suggestions, at our wiki page at https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2017. Informal Registry of Consultants The ArchivesSpace program occasionally gets requests for consulting and other services. Often this is for people who don't want hosting, but need help installing the application, migrating data from a legacy database like Filemaker or a homegrown system, customized training, or custom interface work. While the ArchivesSpace program manages a training program that provides instruction to groups, it can be difficult to keep up with the demand for these kinds of individualized requests, especially when people need onsite services. We'd like to maintain an informal registry of individuals interested in providing consulting services related to ArchivesSpace. The consulting work itself would not be managed by the ArchivesSpace program - consultants and prospective clients would work out any details about the scope of work, deliverables, and compensation amongst themselves. The registry would just be a handy way to gather information about people available to provide services and direct those who are interested to them. If you know of someone, or are interested in this yourself, please email Christine. It would be useful to get the following information: * Location * Services * Experience with ArchivesSpace * Best way for prospective clients to get in touch with you and/or see examples of your work (Affiliation with an ArchivesSpace member institution is not required for an individual to be listed in the registry.) For companies and other larger efforts, we have a Registered Service Provider program with additional benefits. Information about the current program is available at http://archivesspace.org/registered-service-providers/why-and-how-to-become-an-rsp/. Membership Update Our new members since March 6 include: * Amistad Research Center (Louisiana) * Connecticut College * Dakota State University (South Dakota) * Escondido Public Library (California) * Nelson-Atkins Museum of Art (Missouri) * Shippensburg University (Pennsylvania) * University of Hawaii - West O'ahu * William Way LGBT Community Center (Pennsylvania) As of April 10, we have 329 General members, 12 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. Connect with ArchivesSpace in Person Christine, along with Madeline Sheldon of LYRASIS Digital Technology Services and Mary Meyer, LYRASIS Member Outreach Librarian for the Northeast, will be at the Spring meeting of the Mid-Atlantic Regional Archivists Conference in Newark on April 21. Please visit us in the exhibitor area if you have questions or want to chat about your ArchivesSpace experience or if you want to learn more about LYRASIS services. ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA's Collection Management Tools roundtable listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 11964 bytes Desc: image003.jpg URL: From francis.lapka at yale.edu Mon Apr 10 10:52:16 2017 From: francis.lapka at yale.edu (Lapka, Francis) Date: Mon, 10 Apr 2017 14:52:16 +0000 Subject: [Archivesspace_Users_Group] FW: LCNAF plugin Message-ID: I'm sharing a set of related files that illustrate our desired outcomes (should have included this in the initial posting): https://drive.google.com/drive/folders/0B6iyjeOLkTS9R2JIUXFleGNnNGM?usp=sharing You'll see that we want the plug-in to supply the "sort name" rather than have AS try to assemble it. This is especially necessary with complex headings. Our goal is to create a "sort name" that is an exact match for the authorized heading (including the form of punctuation); this is easy accomplished when we grab the form directly from the LC MARCXML. Happy to field other comments or questions. (NB. I initially sent this to the list last week, but I think it failed to post.) Best, Francis -- From: Lapka, Francis Sent: Thursday, April 06, 2017 4:23 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' > Subject: LCNAF plugin As part of a larger project concerning agent and subject records in ArchivesSpace, a group at Yale has drafted changes we'd like to see in the LCNAF plugin (to be coded by a vendor for use at Yale). The spec is outlined here: https://drive.google.com/open?id=1_Jt0_5_9uuu-YexjfIdzTQEuJo2GjQ88no8WxHBXPlI There are three tabs. Text in red indicates changes to existing performance of the plugin (except for the third tab - where we propose an entirely new mapping for lcgft). Some of what we propose may not be universally desired (e.g., using the LC authority URI as AS AuthorityID). Other changes probably ought to be incorporated in the LCNAF plugin for all (e.g., don't create separate AS subject *records* for each variant form in an LCSH record). We welcome your corrections, suggestions, or other thoughts. Thanks, Francis Francis Lapka * Catalog Librarian Dept. of Rare Books and Manuscripts Yale Center for British Art 203.432.9672 * francis.lapka at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From k-miller3 at northwestern.edu Tue Apr 11 12:57:21 2017 From: k-miller3 at northwestern.edu (Karen Miller) Date: Tue, 11 Apr 2017 16:57:21 +0000 Subject: [Archivesspace_Users_Group] LCNAF plugin In-Reply-To: References: Message-ID: <82e30afaa16f4ea2b07386fea46a98c4@evcspmbx05.ads.northwestern.edu> Francis, this is great news and I'm very excited by the prospect of getting an updated plug-in! We're doing a lot of editing when using it now, and the changes you have planned will eliminate a lot of that work for us at Northwestern. I only have two comments on the mappings. 1. I'd rather see contents of the 100$d, 110$d, and 111$d go into the Dates of Existence sub-record instead of Name Forms\Date, since the latter is deprecated. I have mixed feelings about this, though - on the one hand, if there is a 046 present, it may include a more granular date than is in the $d, and it would be a shame to lose that. On the other hand, for many records there is no 046 and only a $d. In these cases, it might be possible to extract appropriate date fields from the $d; Gary Strawn (our former authorities librarian, but still at NUL working archival processing), has written some code that was used to create 046 fields from $d when Library of Congress started automatically converting selected records from AACR2 into RDA. He mentioned that he'd be happy to share it, if it's of interest. 2. I'd also prefer not to strip the terminal periods from 100$, 110$c or 111$c. Although this is listed in your mapping spreadsheet, it does not appear to have been done in the example for the Brown (Family : 1910-1956 : Me.), where the $c is mapped to the Qualifier field as "Me." with the terminal period retained. Finally - and this is just a *thought*, not a suggestion! - at some point in time, it would be wonderful to see the ArchivesSpace Agent record model expanded to accommodate some of the fields that are now being added to name authority records under RDA, such as Fields of Activity, Occupations, Associated Places (including place of birth, place of death, country of residence, headquarters, etc.), Associated Groups, Gender, and Associated Languages. I know this is way, way out of scope for your project, but I thought it might be useful to get it out there and have people start thinking about it. I work in a NACO library where we add loads of information like this to authority record in hopes that it will be used by a discovery system at some point in our lifetimes! Best regards, Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lapka, Francis Sent: Thursday, April 06, 2017 3:23 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] LCNAF plugin As part of a larger project concerning agent and subject records in ArchivesSpace, a group at Yale has drafted changes we'd like to see in the LCNAF plugin (to be coded by a vendor for use at Yale). The spec is outlined here: https://drive.google.com/open?id=1_Jt0_5_9uuu-YexjfIdzTQEuJo2GjQ88no8WxHBXPlI There are three tabs. Text in red indicates changes to existing performance of the plugin (except for the third tab - where we propose an entirely new mapping for lcgft). Some of what we propose may not be universally desired (e.g., using the LC authority URI as AS AuthorityID). Other changes probably ought to be incorporated in the LCNAF plugin for all (e.g., don't create separate AS subject *records* for each variant form in an LCSH record). We welcome your corrections, suggestions, or other thoughts. Thanks, Francis Francis Lapka * Catalog Librarian Dept. of Rare Books and Manuscripts Yale Center for British Art 203.432.9672 * francis.lapka at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Apr 11 16:44:34 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 11 Apr 2017 20:44:34 +0000 Subject: [Archivesspace_Users_Group] Top Container Issues In-Reply-To: References: Message-ID: Dear Marcus, There?s a good deal of information available about top containers and the various container management changes that came in beginning with ArchivesSpace 1.5.0. A few resources to check out: ? The container management screencasts and container management section of the user manual linked from http://docs.archivesspace.org ? Version 1.5.0 preview webinar: http://lyrasis.adobeconnect.com/p4viu8qixrh/ ? Yale commissioned the original plugin and they?ve written the most about the issues they wanted to address and the ways they?ve used the features. They have fairly extensive documentation and screencasts at http://guides.library.yale.edu/archivesspace/ASpaceContainerManagement. One of the advantages of a top container is that you do not have to update multiple records when a box shifts from one place to another in the stacks. You just update the location in the one top container record, so it might help to hear more about what you?re doing now. In general, it might be useful to think of the top container as the highest level container or the external container - the one that holds everything else. It?s somewhat equivalent to Container 1 in previous versions of ArchivesSpace, except it is uniquely identified and identifiable within your database ? which means you can perform bulk operations on containers and even share containers across resources, which you couldn?t easily do before. (The Child and Grandchild fields are equivalent to Container 2 and Container 3 and still operate the same way.) Information such as the barcode, dimensions of the container or its location are stored in the top container record, rather than many different instance records, the way they might have been with the Container 1 model before. I hope this helps. Please feel free to ask more questions if it doesn?t or if you want to know more. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ladd, Marcus Sent: Friday, April 7, 2017 8:30 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Top Container Issues We have just recently upgraded to the most recent version, and we're having problems with how Top Container has merged both Container information and the Location information. For example, our some of our materials move between locations when they are on loan, and with the new structure this would mean we have to recreate the Top Container information every time, rather than just changing the location. Has anyone else encountered similar problems and found a way to make the new structure work? Also, is there specific documentation in one of the updates that explains the Top Container field and what it replaces? thanks, Marcus -------- Marcus Ladd Special Collections Digital Librarian Miami University, Oxford, OH -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 4144 bytes Desc: image003.jpg URL: From francis.lapka at yale.edu Wed Apr 12 13:52:03 2017 From: francis.lapka at yale.edu (Lapka, Francis) Date: Wed, 12 Apr 2017 17:52:03 +0000 Subject: [Archivesspace_Users_Group] LCNAF plugin Message-ID: Thanks Karen. My comments are below. Francis -- Karen Miller k-miller3 at northwestern.edu Tue Apr 11 12:57:21 EDT 2017 Francis, this is great news and I'm very excited by the prospect of getting an updated plug-in! We're doing a lot of editing when using it now, and the changes you have planned will eliminate a lot of that work for us at Northwestern. - FL: Excellent! Yes, our goal is that authorities imported via the plugin will require no (or minimal) manipulation after import. I only have two comments on the mappings. 1. I'd rather see contents of the 100$d, 110$d, and 111$d go into the Dates of Existence sub-record instead of Name Forms\Date, since the latter is deprecated. I have mixed feelings about this, though - on the one hand, if there is a 046 present, it may include a more granular date than is in the $d, and it would be a shame to lose that. On the other hand, for many records there is no 046 and only a $d. In these cases, it might be possible to extract appropriate date fields from the $d; Gary Strawn (our former authorities librarian, but still at NUL working archival processing), has written some code that was used to create 046 fields from $d when Library of Congress started automatically converting selected records from AACR2 into RDA. He mentioned that he'd be happy to share it, if it's of interest. - FL: There is an implicit suggestion in this mapping that deprecation of Name-Forms\Date isn't the correct approach. Here's our thinking: The components of an AS name form are all sub-parts of the access point. If an access point has dates, those dates need to appear in the name form section. Dates that appear in the name form (and part of the access point) aren't necessarily the same as those that represent dates of existence. We may sometimes want to record dates of existence even if dates are not included in the access point. So we need both data elements. This approach parallels what he have in LCNAF, where dates in 1xx $d exist in parallel to dates in 046 - because they mean different things. There is an argument for deriving dates of existence from the dates in the name form (upon import), but our Yale group has opted (so far at least) not to take that option. 2. I'd also prefer not to strip the terminal periods from 100$, 110$c or 111$c. Although this is listed in your mapping spreadsheet, it does not appear to have been done in the example for the Brown (Family : 1910-1956 : Me.), where the $c is mapped to the Qualifier field as "Me." with the terminal period retained. - FL: Yeah, I see the arguments for not stripping those periods. Doing so causes problems with headings such as "$a Seuss, $c Dr." We'll review this. Finally - and this is just a *thought*, not a suggestion! - at some point in time, it would be wonderful to see the ArchivesSpace Agent record model expanded to accommodate some of the fields that are now being added to name authority records under RDA, such as Fields of Activity, Occupations, Associated Places (including place of birth, place of death, country of residence, headquarters, etc.), Associated Groups, Gender, and Associated Languages. I know this is way, way out of scope for your project, but I thought it might be useful to get it out there and have people start thinking about it. I work in a NACO library where we add loads of information like this to authority record in hopes that it will be used by a discovery system at some point in our lifetimes! - FL: I agree! It's my understanding that the AS person model will be modified (before long?) to be compliant with EAC-CPF, providing a richer set of fields, such as those you mention. FL: In my mind, AS might also benefit by reconsidering its treatment of preferred titles. I'd like to see an AS model that recognizes WEMI entities as a separate category of related entity. For the moment, preferred titles without an author can be mapped well enough to AS Subject, of type "preferred title" - though the AS subdivisions for subjects don't work particularly well for titles. For related works that do have an author, I'm not sure what to do. Smoosh them in to an AS subject too (preferred title)? Otherwise, when linking to a work (as subject), we are left to enter the name as a controlled entry in a resource description, with the title dangling as an uncontrolled subdivision (of type "preferred title")- by which practice we lose benefits of treating the whole name/title as a related entity/authority. Best regards, Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lapka, Francis Sent: Thursday, April 06, 2017 3:23 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] LCNAF plugin As part of a larger project concerning agent and subject records in ArchivesSpace, a group at Yale has drafted changes we'd like to see in the LCNAF plugin (to be coded by a vendor for use at Yale). The spec is outlined here: https://drive.google.com/open?id=1_Jt0_5_9uuu-YexjfIdzTQEuJo2GjQ88no8WxHBXPlI> There are three tabs. Text in red indicates changes to existing performance of the plugin (except for the third tab - where we propose an entirely new mapping for lcgft). Some of what we propose may not be universally desired (e.g., using the LC authority URI as AS AuthorityID). Other changes probably ought to be incorporated in the LCNAF plugin for all (e.g., don't create separate AS subject *records* for each variant form in an LCSH record). We welcome your corrections, suggestions, or other thoughts. Thanks, Francis Francis Lapka * Catalog Librarian Dept. of Rare Books and Manuscripts Yale Center for British Art 203.432.9672 * francis.lapka at yale.edu> Francis Lapka * Catalog Librarian Dept. of Rare Books and Manuscripts Yale Center for British Art 203.432.9672 * francis.lapka at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyndi.shein at unlv.edu Wed Apr 12 14:11:39 2017 From: cyndi.shein at unlv.edu (Cyndi Shein) Date: Wed, 12 Apr 2017 11:11:39 -0700 Subject: [Archivesspace_Users_Group] LCNAF plugin In-Reply-To: References: Message-ID: Hello all, Just to weigh in on this conversation, local practice here at UNLV supports Francis' statement: Dates that appear in the name form (and part of the access point) aren?t necessarily the same as those that represent dates of existence. We may sometimes want to record dates of existence even if dates are not included in the access point. So we need both data elements. ?We find that the dates of existence field permits us to include information absent from the authorized heading?... not all headings have dates, and death dates are not often added in a timely manner. ?We're excited about all the developments!? Cyndi Shein Head, Special Collections Technical Services University Libraries, University of Nevada, Las Vegas cyndi.shein at unlv.edu (702) 895-2223 On Wed, Apr 12, 2017 at 10:52 AM, Lapka, Francis wrote: > Thanks Karen. My comments are below. > > > > Francis > > > > > > *--* > > > > *Karen Miller* k-miller3 at northwestern.edu > > *Tue Apr 11 12:57:21 EDT 2017* > > > > Francis, this is great news and I'm very excited by the prospect of getting an updated plug-in! We're doing a lot of editing when using it now, and the changes you have planned will eliminate a lot of that work for us at Northwestern. > > - FL: Excellent! Yes, our goal is that authorities imported via the plugin will require no (or minimal) manipulation after import. > > > > I only have two comments on the mappings. > > > > > > 1. I'd rather see contents of the 100$d, 110$d, and 111$d go into the Dates of Existence sub-record instead of Name Forms\Date, since the latter is deprecated. I have mixed feelings about this, though - on the one hand, if there is a 046 present, it may include a more granular date than is in the $d, and it would be a shame to lose that. On the other hand, for many records there is no 046 and only a $d. In these cases, it might be possible to extract appropriate date fields from the $d; Gary Strawn (our former authorities librarian, but still at NUL working archival processing), has written some code that was used to create 046 fields from $d when Library of Congress started automatically converting selected records from AACR2 into RDA. He mentioned that he'd be happy to share it, if it's of interest. > > - FL: There is an implicit suggestion in this mapping that deprecation of Name-Forms\Date isn?t the correct approach. Here?s our thinking: The components of an AS name form are all sub-parts of the access point. If an access point has dates, those dates need to appear in the name form section. Dates that appear in the name form (and part of the access point) aren?t necessarily the same as those that represent dates of existence. We may sometimes want to record dates of existence even if dates are not included in the access point. So we need both data elements. This approach parallels what he have in LCNAF, where dates in 1xx $d exist in parallel to dates in 046 ? because they mean different things. There is an argument for deriving dates of existence from the dates in the name form (upon import), but our Yale group has opted (so far at least) not to take that option. > > > > > > 2. I'd also prefer not to strip the terminal periods from 100$, 110$c or 111$c. Although this is listed in your mapping spreadsheet, it does not appear to have been done in the example for the Brown (Family : 1910-1956 : Me.), where the $c is mapped to the Qualifier field as "Me." with the terminal period retained. > > - FL: Yeah, I see the arguments for not stripping those periods. Doing so causes problems with headings such as ?$a Seuss, $c Dr.? We?ll review this. > > > > Finally - and this is just a *thought*, not a suggestion! - at some point in time, it would be wonderful to see the ArchivesSpace Agent record model expanded to accommodate some of the fields that are now being added to name authority records under RDA, such as Fields of Activity, Occupations, Associated Places (including place of birth, place of death, country of residence, headquarters, etc.), Associated Groups, Gender, and Associated Languages. I know this is way, way out of scope for your project, but I thought it might be useful to get it out there and have people start thinking about it. I work in a NACO library where we add loads of information like this to authority record in hopes that it will be used by a discovery system at some point in our lifetimes! > > - FL: I agree! It?s my understanding that the AS person model will be modified (before long?) to be compliant with EAC-CPF, providing a richer set of fields, such as those you mention. > > > > FL: In my mind, AS might also benefit by reconsidering its treatment of preferred titles. I?d like to see an AS model that recognizes WEMI entities as a separate category of related entity. For the moment, preferred titles *without an author *can be mapped well enough to AS Subject, of type ?preferred title? ? though the AS subdivisions for subjects don?t work particularly well for titles. For related works that do have an author, I?m not sure what to do. Smoosh them in to an AS subject too (preferred title)? Otherwise, when linking to a work (as subject), we are left to enter the name as a controlled entry in a resource description, with the title dangling as an uncontrolled subdivision (of type ?preferred title?)? by which practice we lose benefits of treating the whole name/title as a related entity/authority. > > > > > > > > > > Best regards, > > Karen > > > > Karen D. Miller > > Monographic Cataloger/Metadata Specialist > > Northwestern University Libraries > > Northwestern University > > 1970 Campus Drive > > Evanston, IL 60208 > > www.library.northwestern.edu > > k-miller3 at northwestern.edu > > 874.467.3462 > > > > > > > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org ] On Behalf Of Lapka, Francis > > Sent: Thursday, April 06, 2017 3:23 PM > > To: archivesspace_users_group at lyralists.lyrasis.org > > Subject: [Archivesspace_Users_Group] LCNAF plugin > > > > As part of a larger project concerning agent and subject records in ArchivesSpace, a group at Yale has drafted changes we'd like to see in the LCNAF plugin (to be coded by a vendor for use at Yale). The spec is outlined here: > > > > https://drive.google.com/open?id=1_Jt0_5_9uuu-YexjfIdzTQEuJo2GjQ88no8WxHBXPlI > > > > There are three tabs. Text in red indicates changes to existing performance of the plugin (except for the third tab - where we propose an entirely new mapping for lcgft). > > > > Some of what we propose may not be universally desired (e.g., using the LC authority URI as AS AuthorityID). Other changes probably ought to be incorporated in the LCNAF plugin for all (e.g., don't create separate AS subject *records* for each variant form in an LCSH record). > > > > We welcome your corrections, suggestions, or other thoughts. > > > > Thanks, > > Francis > > > > > > Francis Lapka * Catalog Librarian > > Dept. of Rare Books and Manuscripts > > Yale Center for British Art > > 203.432.9672 <%28203%29%20432-9672> * francis.lapka at yale.edu > > > > > > > Francis Lapka ? Catalog Librarian > > Dept. of Rare Books and Manuscripts > > Yale Center for British Art > > 203.432.9672 <%28203%29%20432-9672> ? francis.lapka at yale.edu > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 11771 bytes Desc: not available URL: From christine.dibella at lyrasis.org Wed Apr 12 15:30:52 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 12 Apr 2017 19:30:52 +0000 Subject: [Archivesspace_Users_Group] LCNAF plugin In-Reply-To: References: Message-ID: This is really wonderful work and discussion. Thank you all for these efforts! I wanted to mention a few things related to ongoing ArchivesSpace development and a few of the points in the discussion. ? There are several related JIRA issues related to the Dates/Dates of Existence issue specifically: https://archivesspace.atlassian.net/browse/AR-1322, https://archivesspace.atlassian.net/browse/AR-1339, and https://archivesspace.atlassian.net/browse/AR-1344. ? The Dates field is the Agent record is no longer deprecated. This decision was made awhile back, but the tooltip and documentation are just catching up with the 2.0.0 version. The short version of why this is the case is that in the current application, the Dates field is needed for alignment with MARC while the Dates of Existence fields align better with EAC-CPF and allow for more precise use of dates. Currently what is in the Dates field is also what is put into the display string for an Agent, on both the staff interface and the public interface. While it is certainly not the most satisfying answer, the current solution is to either use both sets of dates, or to choose the one that most reflects your intended output. ? As Francis suggests, a more robust Agents module is in the planning stages. Cory Nimer and Brad Westbrook have been working on specification for a substantial reworking of the Agents module, along with fuller support for EAC-CPF. I believe this specification will be ready for wider community review soon. In addition to providing the potential for recording additional types of information about people, families, and corporate bodies, reworking the Agents module could potentially come up with a solution for this date redundancy problem, though from this discussion it sounds like there are use cases for maintaining both ways to record dates. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Cyndi Shein Sent: Wednesday, April 12, 2017 2:12 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] LCNAF plugin Hello all, Just to weigh in on this conversation, local practice here at UNLV supports Francis' statement: Dates that appear in the name form (and part of the access point) aren?t necessarily the same as those that represent dates of existence. We may sometimes want to record dates of existence even if dates are not included in the access point. So we need both data elements. ?We find that the dates of existence field permits us to include information absent from the authorized heading?... not all headings have dates, and death dates are not often added in a timely manner. ?We're excited about all the developments!? Cyndi Shein Head, Special Collections Technical Services University Libraries, University of Nevada, Las Vegas cyndi.shein at unlv.edu (702) 895-2223 [cid:image002.jpg at 01D2B3A1.73D87D80] On Wed, Apr 12, 2017 at 10:52 AM, Lapka, Francis > wrote: Thanks Karen. My comments are below. Francis -- Karen Miller k-miller3 at northwestern.edu Tue Apr 11 12:57:21 EDT 2017 Francis, this is great news and I'm very excited by the prospect of getting an updated plug-in! We're doing a lot of editing when using it now, and the changes you have planned will eliminate a lot of that work for us at Northwestern. - FL: Excellent! Yes, our goal is that authorities imported via the plugin will require no (or minimal) manipulation after import. I only have two comments on the mappings. 1. I'd rather see contents of the 100$d, 110$d, and 111$d go into the Dates of Existence sub-record instead of Name Forms\Date, since the latter is deprecated. I have mixed feelings about this, though - on the one hand, if there is a 046 present, it may include a more granular date than is in the $d, and it would be a shame to lose that. On the other hand, for many records there is no 046 and only a $d. In these cases, it might be possible to extract appropriate date fields from the $d; Gary Strawn (our former authorities librarian, but still at NUL working archival processing), has written some code that was used to create 046 fields from $d when Library of Congress started automatically converting selected records from AACR2 into RDA. He mentioned that he'd be happy to share it, if it's of interest. - FL: There is an implicit suggestion in this mapping that deprecation of Name-Forms\Date isn?t the correct approach. Here?s our thinking: The components of an AS name form are all sub-parts of the access point. If an access point has dates, those dates need to appear in the name form section. Dates that appear in the name form (and part of the access point) aren?t necessarily the same as those that represent dates of existence. We may sometimes want to record dates of existence even if dates are not included in the access point. So we need both data elements. This approach parallels what he have in LCNAF, where dates in 1xx $d exist in parallel to dates in 046 ? because they mean different things. There is an argument for deriving dates of existence from the dates in the name form (upon import), but our Yale group has opted (so far at least) not to take that option. 2. I'd also prefer not to strip the terminal periods from 100$, 110$c or 111$c. Although this is listed in your mapping spreadsheet, it does not appear to have been done in the example for the Brown (Family : 1910-1956 : Me.), where the $c is mapped to the Qualifier field as "Me." with the terminal period retained. - FL: Yeah, I see the arguments for not stripping those periods. Doing so causes problems with headings such as ?$a Seuss, $c Dr.? We?ll review this. Finally - and this is just a *thought*, not a suggestion! - at some point in time, it would be wonderful to see the ArchivesSpace Agent record model expanded to accommodate some of the fields that are now being added to name authority records under RDA, such as Fields of Activity, Occupations, Associated Places (including place of birth, place of death, country of residence, headquarters, etc.), Associated Groups, Gender, and Associated Languages. I know this is way, way out of scope for your project, but I thought it might be useful to get it out there and have people start thinking about it. I work in a NACO library where we add loads of information like this to authority record in hopes that it will be used by a discovery system at some point in our lifetimes! - FL: I agree! It?s my understanding that the AS person model will be modified (before long?) to be compliant with EAC-CPF, providing a richer set of fields, such as those you mention. FL: In my mind, AS might also benefit by reconsidering its treatment of preferred titles. I?d like to see an AS model that recognizes WEMI entities as a separate category of related entity. For the moment, preferred titles without an author can be mapped well enough to AS Subject, of type ?preferred title? ? though the AS subdivisions for subjects don?t work particularly well for titles. For related works that do have an author, I?m not sure what to do. Smoosh them in to an AS subject too (preferred title)? Otherwise, when linking to a work (as subject), we are left to enter the name as a controlled entry in a resource description, with the title dangling as an uncontrolled subdivision (of type ?preferred title?)? by which practice we lose benefits of treating the whole name/title as a related entity/authority. Best regards, Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lapka, Francis Sent: Thursday, April 06, 2017 3:23 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] LCNAF plugin As part of a larger project concerning agent and subject records in ArchivesSpace, a group at Yale has drafted changes we'd like to see in the LCNAF plugin (to be coded by a vendor for use at Yale). The spec is outlined here: https://drive.google.com/open?id=1_Jt0_5_9uuu-YexjfIdzTQEuJo2GjQ88no8WxHBXPlI> There are three tabs. Text in red indicates changes to existing performance of the plugin (except for the third tab - where we propose an entirely new mapping for lcgft). Some of what we propose may not be universally desired (e.g., using the LC authority URI as AS AuthorityID). Other changes probably ought to be incorporated in the LCNAF plugin for all (e.g., don't create separate AS subject *records* for each variant form in an LCSH record). We welcome your corrections, suggestions, or other thoughts. Thanks, Francis Francis Lapka * Catalog Librarian Dept. of Rare Books and Manuscripts Yale Center for British Art 203.432.9672 * francis.lapka at yale.edu> Francis Lapka ? Catalog Librarian Dept. of Rare Books and Manuscripts Yale Center for British Art 203.432.9672 ? francis.lapka at yale.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 1497 bytes Desc: image002.jpg URL: From noah.huffman at duke.edu Wed Apr 12 16:30:18 2017 From: noah.huffman at duke.edu (Noah Huffman) Date: Wed, 12 Apr 2017 20:30:18 +0000 Subject: [Archivesspace_Users_Group] Seeking feedback on EAD3 export mappings for ArchivesSpace Message-ID: The Migrations Subteam of the Technical Advisory Council is interested in your feedback on a draft specification for exporting EAD3 from ArchivesSpace (see the third tab). One of the subteam's goals is to advance support for EAD3 in ArchivesSpace generally. To that end, we've also developed some guiding principles for EAD3 support. Please feel free to add comments to both the mapping spreadsheet and the guiding principles document. If you prefer, you can also email your comments to me. Our hope is to finalize the export mappings document fairly soon and then hand it off to the Prioritization sub-team where it can be scheduled for development. Here is a placeholder JIRA issue if you want to follow progress on EAD3 support in ASpace: https://archivesspace.atlassian.net/browse/AR-923 Thanks! -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From k-miller3 at northwestern.edu Wed Apr 12 17:33:45 2017 From: k-miller3 at northwestern.edu (Karen Miller) Date: Wed, 12 Apr 2017 21:33:45 +0000 Subject: [Archivesspace_Users_Group] LCNAF plugin In-Reply-To: References: Message-ID: <312b77a0e4bf4d6cafee3087a2dff877@evcspmbx05.ads.northwestern.edu> Francis, We also have the problem of preferred titles that do have an author. For now, we've treated them by smooshing them into an Agent record, but I could see smooshing them into a Subject instead. I see your point about mapping the 046 field to the Dates of Existence record; sometimes these differ in granularity from what's in the $d. Sometimes there is a 046 but no $d, and sometimes there is a $d but no 046....so we really can't assume a one-to-one relationship. Karen From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lapka, Francis Sent: Wednesday, April 12, 2017 12:52 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] LCNAF plugin Thanks Karen. My comments are below. Francis -- Karen Miller k-miller3 at northwestern.edu Tue Apr 11 12:57:21 EDT 2017 Francis, this is great news and I'm very excited by the prospect of getting an updated plug-in! We're doing a lot of editing when using it now, and the changes you have planned will eliminate a lot of that work for us at Northwestern. - FL: Excellent! Yes, our goal is that authorities imported via the plugin will require no (or minimal) manipulation after import. I only have two comments on the mappings. 1. I'd rather see contents of the 100$d, 110$d, and 111$d go into the Dates of Existence sub-record instead of Name Forms\Date, since the latter is deprecated. I have mixed feelings about this, though - on the one hand, if there is a 046 present, it may include a more granular date than is in the $d, and it would be a shame to lose that. On the other hand, for many records there is no 046 and only a $d. In these cases, it might be possible to extract appropriate date fields from the $d; Gary Strawn (our former authorities librarian, but still at NUL working archival processing), has written some code that was used to create 046 fields from $d when Library of Congress started automatically converting selected records from AACR2 into RDA. He mentioned that he'd be happy to share it, if it's of interest. - FL: There is an implicit suggestion in this mapping that deprecation of Name-Forms\Date isn't the correct approach. Here's our thinking: The components of an AS name form are all sub-parts of the access point. If an access point has dates, those dates need to appear in the name form section. Dates that appear in the name form (and part of the access point) aren't necessarily the same as those that represent dates of existence. We may sometimes want to record dates of existence even if dates are not included in the access point. So we need both data elements. This approach parallels what he have in LCNAF, where dates in 1xx $d exist in parallel to dates in 046 - because they mean different things. There is an argument for deriving dates of existence from the dates in the name form (upon import), but our Yale group has opted (so far at least) not to take that option. 2. I'd also prefer not to strip the terminal periods from 100$, 110$c or 111$c. Although this is listed in your mapping spreadsheet, it does not appear to have been done in the example for the Brown (Family : 1910-1956 : Me.), where the $c is mapped to the Qualifier field as "Me." with the terminal period retained. - FL: Yeah, I see the arguments for not stripping those periods. Doing so causes problems with headings such as "$a Seuss, $c Dr." We'll review this. Finally - and this is just a *thought*, not a suggestion! - at some point in time, it would be wonderful to see the ArchivesSpace Agent record model expanded to accommodate some of the fields that are now being added to name authority records under RDA, such as Fields of Activity, Occupations, Associated Places (including place of birth, place of death, country of residence, headquarters, etc.), Associated Groups, Gender, and Associated Languages. I know this is way, way out of scope for your project, but I thought it might be useful to get it out there and have people start thinking about it. I work in a NACO library where we add loads of information like this to authority record in hopes that it will be used by a discovery system at some point in our lifetimes! - FL: I agree! It's my understanding that the AS person model will be modified (before long?) to be compliant with EAC-CPF, providing a richer set of fields, such as those you mention. FL: In my mind, AS might also benefit by reconsidering its treatment of preferred titles. I'd like to see an AS model that recognizes WEMI entities as a separate category of related entity. For the moment, preferred titles without an author can be mapped well enough to AS Subject, of type "preferred title" - though the AS subdivisions for subjects don't work particularly well for titles. For related works that do have an author, I'm not sure what to do. Smoosh them in to an AS subject too (preferred title)? Otherwise, when linking to a work (as subject), we are left to enter the name as a controlled entry in a resource description, with the title dangling as an uncontrolled subdivision (of type "preferred title")- by which practice we lose benefits of treating the whole name/title as a related entity/authority. Best regards, Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lapka, Francis Sent: Thursday, April 06, 2017 3:23 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] LCNAF plugin As part of a larger project concerning agent and subject records in ArchivesSpace, a group at Yale has drafted changes we'd like to see in the LCNAF plugin (to be coded by a vendor for use at Yale). The spec is outlined here: https://drive.google.com/open?id=1_Jt0_5_9uuu-YexjfIdzTQEuJo2GjQ88no8WxHBXPlI> There are three tabs. Text in red indicates changes to existing performance of the plugin (except for the third tab - where we propose an entirely new mapping for lcgft). Some of what we propose may not be universally desired (e.g., using the LC authority URI as AS AuthorityID). Other changes probably ought to be incorporated in the LCNAF plugin for all (e.g., don't create separate AS subject *records* for each variant form in an LCSH record). We welcome your corrections, suggestions, or other thoughts. Thanks, Francis Francis Lapka * Catalog Librarian Dept. of Rare Books and Manuscripts Yale Center for British Art 203.432.9672 * francis.lapka at yale.edu> Francis Lapka * Catalog Librarian Dept. of Rare Books and Manuscripts Yale Center for British Art 203.432.9672 * francis.lapka at yale.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From gpgaidmore at wm.edu Wed Apr 12 21:06:03 2017 From: gpgaidmore at wm.edu (Gaidmore, Gerald) Date: Thu, 13 Apr 2017 01:06:03 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Technical Advisory Council Message-ID: Just wanted to clarify that while only ArchivesSpace member representatives can suggest nominees to the TAC, nominees do not necessarily have to be from ArchivesSpace member institutions. Thanks, 2017 ArchivesSpace Nominating Committee From: Gaidmore, Gerald Sent: Friday, April 07, 2017 7:54 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: Nominations Requested for ArchivesSpace Technical Advisory Council The ArchivesSpace Governance Board is looking for nominations to fill up to 7 vacancies on the ArchivesSpace Technical Advisory Council (TAC). Nominees should be presently employed at an ArchivesSpace member institution in the Very Large, Large, Medium, Small, or Very Small levels (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). They may also be employees of a current Registered Service Provider (see: http://archivesspace.org/registered-service-providers/current-rsps/). Nominations may be made only by ArchivesSpace Member Representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities assigned to TAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 28. The Nominating Committee will review all nominations and recommend appointments to the Governance Board for approval. TAC (http://archivesspace.org/governance-board-and-councils/#TAC) is a critical part of the ArchivesSpace community, having responsibility for providing technical guidance to individuals or organizations contributing to application development, to the User Advisory Council, and to the ArchivesSpace Governance Board. TAC's current activities include: * developing a community of code committers, including helping to establish guidelines for contributing code and reviewing contributions, * reviewing enhancements and priorities, and testing in collaboration with the User Advisory Council, * providing support for migrating data to ArchivesSpace from other systems and support for importing and exporting data such as EAD, MARCXML, CSV * documenting and assisting with resolving bugs identified in the application, * identifying integration points for ArchivesSpace with other systems (e.g. digital asset management systems, patron and request management systems, etc.), creating resources to assist the community with integration work and, for specific integrations, developing technical requirements, and * updating technical documentation. Sub-teams will be established within TAC to address the areas identified above, as well other activity areas identified subsequently. Nominees must have sufficient knowledge of application development methods, architectures and coding practices to participate in and lead some of the identified activities. Nominees with experience in open source projects, developing web applications (particularly using Ruby on Rails and Sinatra), software testing, or interest in those areas, are especially welcome. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service for these appointments will be July 1, 2017-June 30, 2019. We expect to make up to 7 appointments, and each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2019-June 30, 2021. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicating the areas of activity to which the nominee is prepared to contribute. Again, self-nominations are also welcome. Return the completed form via email to the ArchivesSpace Program Manager, Christine Di Bella (christine.dibella at lyrasis.org), who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 28. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, Jay Gaidmore The College of William & Mary Chair, and Governance Board member On behalf of Nominating Committee members: Gordon Daines, Brigham Young University, Chair of User Advisory Council Sally Vermaaten, Gates Archive, Chair of Technical Advisory Council Johna Von Behrens, University of Louisiana Lafayette, representing Very Large membership level Cyndi Shein, UNLV, representing Large membership level Mary Saffell, Texas Christian University, representing Medium membership level Julia Novakovic, The Strong National Museum of Play, representing Small membership level Annie Tummino, SUNY Maritime, representing Very Small membership level Christine Di Bella, ArchivesSpace Program Manager, ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Managing/endorsing/eliciting code contributions ___Application testing ___Migration issues, including import/exports and API design and implementation ___Bug fixes ___Program architecture and integrations with other software ___Technical documentation -------------- next part -------------- An HTML attachment was scrubbed... URL: From jane.labarbara at mail.wvu.edu Thu Apr 13 12:34:23 2017 From: jane.labarbara at mail.wvu.edu (Jane LaBarbara) Date: Thu, 13 Apr 2017 16:34:23 +0000 Subject: [Archivesspace_Users_Group] Accessions CSV template and telephone numbers Message-ID: All, Has anyone successfully used the Accessions CSV template to add accession records with agent records that include telephone numbers? I've done a few test imports, but I can't seem to get the telephone numbers to import at all-the rest of the agent contact info imports as expected. I've tried entering them with dashes and without. (This isn't the end of the world, just 240 telephone numbers I'd rather not enter by hand.) If anyone's found a nice solution or workaround, I'd be glad to hear it. Thanks, Jane / Jane Metters LaBarbara Assistant Curator, West Virginia & Regional History Center West Virginia University Libraries (304) 293-0352 office jane.labarbara at mail.wvu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Thu Apr 13 12:43:45 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 13 Apr 2017 16:43:45 +0000 Subject: [Archivesspace_Users_Group] call for ArchivesSpace Member Forum 2017 speakers and topics Message-ID: Hello ArchivesSpace members, ArchivesSpace will be holding its third annual Member Forum on July 25, 2017, at Portland State University in Portland, Oregon. Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. More information on the developing program is on the ArchivesSpace wiki at https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2017. The planning group is looking for speakers to cover a range of topics. We've suggested a few on the wiki page, but anything related to ArchivesSpace is fair game. We're looking for speakers for the proposed topics, as well as suggestions for more topics you'd like to learn or talk about at the meeting in half-day workshops in the morning, and plenary (full group) sessions or small group sessions in the afternoon. Afternoon sessions may take any one of a number of formats, including panels, lightning rounds, and discussion groups. There is a short Google submission form available at https://goo.gl/WWrjQt; you can submit ideas or volunteer yourself to speak either via the form or by emailing me directly. Proposals, ideas, and suggestions received by May 5 will receive priority consideration so that we can get the program squared away as soon as possible. If you have any questions or other suggestions at this point, please just let me know. Registration for the Member Forum will open later this spring. Thanks in advance for your help in making this a great event! Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 4144 bytes Desc: image003.jpg URL: From christine.dibella at lyrasis.org Thu Apr 13 13:58:08 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 13 Apr 2017 17:58:08 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.0.0-RC2 Message-ID: Dear ArchivesSpace members, Thank you so much to all who submitted feedback on v2.0.0-RC1. Your efforts have been absolutely crucial in helping us identify and address a number of bugs and performance issues prior to the production version of this major release. Because issues were addressed throughout the application, we have decided to make an additional release candidate available for a short period of time. V2.0.0-RC2 (https://github.com/archivesspace/archivesspace/releases/tag/v2.0.0-RC2) is now available for download and testing purposes. We are collecting feedback until Monday, April 17. Please email me directly with any issues or questions. Thanks again for your efforts and feedback. Barring unforeseen issues, we expect the production release of 2.0.0 to come out next week. The next major release of ArchivesSpace, 2.1.0, is anticipated to come in June. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 4144 bytes Desc: image002.jpg URL: From noah.huffman at duke.edu Thu Apr 13 14:55:20 2017 From: noah.huffman at duke.edu (Noah Huffman) Date: Thu, 13 Apr 2017 18:55:20 +0000 Subject: [Archivesspace_Users_Group] Accessions CSV template and telephone numbers In-Reply-To: References: Message-ID: Hi Jane, I'm not able to import phone numbers using the Accession CSV importer either. I think there were some changes to the data model several releases ago that affected the way telephone numbers are stored. See: https://archivesspace.atlassian.net/browse/AR-1156 and https://archivesspace.atlassian.net/browse/AR-1229 My guess is that the Accession CSV importer (converter) was never updated to reflect the data model changes. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jane LaBarbara Sent: Thursday, April 13, 2017 12:34 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Accessions CSV template and telephone numbers All, Has anyone successfully used the Accessions CSV template to add accession records with agent records that include telephone numbers? I've done a few test imports, but I can't seem to get the telephone numbers to import at all-the rest of the agent contact info imports as expected. I've tried entering them with dashes and without. (This isn't the end of the world, just 240 telephone numbers I'd rather not enter by hand.) If anyone's found a nice solution or workaround, I'd be glad to hear it. Thanks, Jane / Jane Metters LaBarbara Assistant Curator, West Virginia & Regional History Center West Virginia University Libraries (304) 293-0352 office jane.labarbara at mail.wvu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael_vandermillen at harvard.edu Thu Apr 13 16:04:54 2017 From: michael_vandermillen at harvard.edu (Vandermillen, Michael) Date: Thu, 13 Apr 2017 20:04:54 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.0.0-RC2 In-Reply-To: References: Message-ID: Hi, RC 2 release notes say you'll need to build from source with environment variable set for the new PUI, but not the notes from RC 1 (sorry if I missed it); so should RC 1 work setting the variable with the aspace release, or do we need to build that as well? Thanks- Michael From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Thursday, April 13, 2017 1:58 PM To: Archivesspace Users Group ; Archivesspace Member Reps ; archivesspace_tac_uac at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.0.0-RC2 Dear ArchivesSpace members, Thank you so much to all who submitted feedback on v2.0.0-RC1. Your efforts have been absolutely crucial in helping us identify and address a number of bugs and performance issues prior to the production version of this major release. Because issues were addressed throughout the application, we have decided to make an additional release candidate available for a short period of time. V2.0.0-RC2 (https://github.com/archivesspace/archivesspace/releases/tag/v2.0.0-RC2) is now available for download and testing purposes. We are collecting feedback until Monday, April 17. Please email me directly with any issues or questions. Thanks again for your efforts and feedback. Barring unforeseen issues, we expect the production release of 2.0.0 to come out next week. The next major release of ArchivesSpace, 2.1.0, is anticipated to come in June. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Thu Apr 13 16:25:29 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 13 Apr 2017 20:25:29 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.0.0-RC2 Message-ID: Hi Michael, Yes, we've clarified in these release notes that you need to build from source and set the environment variable yourself if you want to test out the beta PUI with your own data. This was the case with RC1 as well, but the release notes did not make that distinction. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Vandermillen, Michael Sent: Thursday, April 13, 2017 4:05 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.0.0-RC2 Hi, RC 2 release notes say you'll need to build from source with environment variable set for the new PUI, but not the notes from RC 1 (sorry if I missed it); so should RC 1 work setting the variable with the aspace release, or do we need to build that as well? Thanks- Michael From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Thursday, April 13, 2017 1:58 PM To: Archivesspace Users Group >; Archivesspace Member Reps >; archivesspace_tac_uac at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.0.0-RC2 Dear ArchivesSpace members, Thank you so much to all who submitted feedback on v2.0.0-RC1. Your efforts have been absolutely crucial in helping us identify and address a number of bugs and performance issues prior to the production version of this major release. Because issues were addressed throughout the application, we have decided to make an additional release candidate available for a short period of time. V2.0.0-RC2 (https://github.com/archivesspace/archivesspace/releases/tag/v2.0.0-RC2) is now available for download and testing purposes. We are collecting feedback until Monday, April 17. Please email me directly with any issues or questions. Thanks again for your efforts and feedback. Barring unforeseen issues, we expect the production release of 2.0.0 to come out next week. The next major release of ArchivesSpace, 2.1.0, is anticipated to come in June. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: From michael_vandermillen at harvard.edu Thu Apr 13 20:03:12 2017 From: michael_vandermillen at harvard.edu (Vandermillen, Michael) Date: Fri, 14 Apr 2017 00:03:12 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.0.0-RC2 In-Reply-To: References: Message-ID: Ok, thanks, we'll build! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Thursday, April 13, 2017 4:25 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.0.0-RC2 Hi Michael, Yes, we've clarified in these release notes that you need to build from source and set the environment variable yourself if you want to test out the beta PUI with your own data. This was the case with RC1 as well, but the release notes did not make that distinction. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Vandermillen, Michael Sent: Thursday, April 13, 2017 4:05 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.0.0-RC2 Hi, RC 2 release notes say you'll need to build from source with environment variable set for the new PUI, but not the notes from RC 1 (sorry if I missed it); so should RC 1 work setting the variable with the aspace release, or do we need to build that as well? Thanks- Michael From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Thursday, April 13, 2017 1:58 PM To: Archivesspace Users Group >; Archivesspace Member Reps >; archivesspace_tac_uac at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.0.0-RC2 Dear ArchivesSpace members, Thank you so much to all who submitted feedback on v2.0.0-RC1. Your efforts have been absolutely crucial in helping us identify and address a number of bugs and performance issues prior to the production version of this major release. Because issues were addressed throughout the application, we have decided to make an additional release candidate available for a short period of time. V2.0.0-RC2 (https://github.com/archivesspace/archivesspace/releases/tag/v2.0.0-RC2) is now available for download and testing purposes. We are collecting feedback until Monday, April 17. Please email me directly with any issues or questions. Thanks again for your efforts and feedback. Barring unforeseen issues, we expect the production release of 2.0.0 to come out next week. The next major release of ArchivesSpace, 2.1.0, is anticipated to come in June. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: From ltang5 at mail.lib.msu.edu Fri Apr 14 11:34:35 2017 From: ltang5 at mail.lib.msu.edu (Tang, Lydia) Date: Fri, 14 Apr 2017 15:34:35 +0000 Subject: [Archivesspace_Users_Group] Beta PUI snag Message-ID: <9CBEEF82-7A6E-458F-815A-F5814B3A5DC0@mail.lib.msu.edu> With my very limited technical understanding of the ASpace backend, I just wanted to pass along from my IT team that we attempted to implement the Beta PUI on our test instance but it caused an internal server error. My IT person described that the instructions for the PUI were for an older version of ASpace (not the 2.0.0 RC2) and were too general to use. I just wanted to voice this to the community, in case others also have issues trying out the beta PUI or if anyone has any suggestions for implementing it. Thanks! Lydia From mark.cooper at lyrasis.org Fri Apr 14 12:18:15 2017 From: mark.cooper at lyrasis.org (Mark Cooper) Date: Fri, 14 Apr 2017 16:18:15 +0000 Subject: [Archivesspace_Users_Group] Beta PUI snag In-Reply-To: <9CBEEF82-7A6E-458F-815A-F5814B3A5DC0@mail.lib.msu.edu> References: <9CBEEF82-7A6E-458F-815A-F5814B3A5DC0@mail.lib.msu.edu> Message-ID: Hi Lydia, I just made a build on my laptop and it worked, here are the rough steps: Stop any currently running instances of aspace and backup / remove the aspace folder Set the ASPACE_PUBLIC_NEW environment variable to "true" and confirm it's present Start with a new checkout of the aspace source code (you must use source, not the RC zip) >From the aspace source folder do: ./scripts/build_release -t Wait for the build to complete Unzip the new release (where you had aspace previously) and restore config.rb and mysql connector as needed Make sure ASPACE_PUBLIC_NEW is still present (needed to disable known incompatible plugins) Fire it up And it think it's already clear but the new PUI is very much beta, not for production use yet. Best, Mark Mark Cooper Technical Lead, Hosting and Support LYRASIS email: mark.cooper at lyrasis.org skype: mark_c_cooper ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tang, Lydia Sent: Friday, April 14, 2017 8:34:35 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Beta PUI snag With my very limited technical understanding of the ASpace backend, I just wanted to pass along from my IT team that we attempted to implement the Beta PUI on our test instance but it caused an internal server error. My IT person described that the instructions for the PUI were for an older version of ASpace (not the 2.0.0 RC2) and were too general to use. I just wanted to voice this to the community, in case others also have issues trying out the beta PUI or if anyone has any suggestions for implementing it. Thanks! Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at eservices.virginia.edu Fri Apr 14 15:06:16 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 14 Apr 2017 19:06:16 +0000 Subject: [Archivesspace_Users_Group] Beta PUI snag In-Reply-To: References: <9CBEEF82-7A6E-458F-815A-F5814B3A5DC0@mail.lib.msu.edu> Message-ID: <230B91C4-32B5-4E42-996E-FA71CCD1D5E4@eservices.virginia.edu> I have a branch here that modifies the build to create both public.war and public-new.war and run them both by default: old public on port 8081, new public on port 8082: https://github.com/uvalib/archivesspace/tree/new-pui-build with these changes to the default config: diff --git a/common/config/config-defaults.rb b/common/config/config-defaults.rb index 4697548..a8db378 100644 --- a/common/config/config-defaults.rb +++ b/common/config/config-defaults.rb @@ -145,7 +145,7 @@ AppConfig[:report_pdf_font_family] = "\"DejaVu Sans\", sans-serif" # Plug-ins to load. They will load in the order specified AppConfig[:plugins] = ['local', 'lcnaf'] # The aspace-public-formats plugin is not supported in the new public application -AppConfig[:plugins] << 'aspace-public-formats' unless ENV['ASPACE_PUBLIC_NEW'] == 'true' +# AppConfig[:plugins] << 'aspace-public-formats' unless ENV['ASPACE_PUBLIC_NEW'] == 'true' # URL to direct the feedback link # You can remove this from the footer by making the value blank. @@ -432,3 +432,5 @@ AppConfig[:pui_email_enabled] = false #} #AppConfig[:pui_email_perform_deliveries] = true #AppConfig[:pui_email_raise_delivery_errors] = true +AppConfig[:public_new_url] = "http://localhost:8082" +AppConfig[:enable_public_new] = true So no setting of environment variables required, and you can evaluate new PUI while still running old. Minimally tested so far, so I don?t yet know if there is a flaw in this scheme due to any resource conflicts. I still need to fix the public:deverver targets, but building and running the distribution seems to be working ok for me. Launcher uses these AppConfig values, so you can turn this option on or off ( on by default ): diff --git a/launcher/launcher.rb b/launcher/launcher.rb index 3cba660..239c60b 100644 --- a/launcher/launcher.rb +++ b/launcher/launcher.rb @@ -170,6 +170,10 @@ def main {:war => File.join(aspace_base,'wars', 'public.war'), :path => '/'}, {:static_dirs => ASUtils.find_local_directories("public/assets"), :path => "#{AppConfig[:public_prefix]}assets"}) if AppConfig[:enable_public] + start_server(URI(AppConfig[:public_new_url]).port, + {:war => File.join(aspace_base,'wars', 'public-new.war'), :path => '/'}, + {:static_dirs => ASUtils.find_local_directories("public/assets"), + :path => "#{AppConfig[:public_prefix]}assets"}) if AppConfig[:enable_public_new] start_server(URI(AppConfig[:docs_url]).port, {:static_dirs => File.join(aspace_base,"docs", "_site"), :path => '/archivesspace'}) if AppConfig[:enable_docs] rescue Note that there are no duplicate config options for public proxy, prefix, theme or other options. ? Steve Majewski / UVA Alderman Library On Apr 14, 2017, at 12:18 PM, Mark Cooper > wrote: Hi Lydia, I just made a build on my laptop and it worked, here are the rough steps: Stop any currently running instances of aspace and backup / remove the aspace folder Set the ASPACE_PUBLIC_NEW environment variable to "true" and confirm it's present Start with a new checkout of the aspace source code (you must use source, not the RC zip) From the aspace source folder do: ./scripts/build_release -t Wait for the build to complete Unzip the new release (where you had aspace previously) and restore config.rb and mysql connector as needed Make sure ASPACE_PUBLIC_NEW is still present (needed to disable known incompatible plugins) Fire it up And it think it's already clear but the new PUI is very much beta, not for production use yet. Best, Mark Mark Cooper Technical Lead, Hosting and Support LYRASIS email: mark.cooper at lyrasis.org skype: mark_c_cooper ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Tang, Lydia > Sent: Friday, April 14, 2017 8:34:35 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Beta PUI snag With my very limited technical understanding of the ASpace backend, I just wanted to pass along from my IT team that we attempted to implement the Beta PUI on our test instance but it caused an internal server error. My IT person described that the instructions for the PUI were for an older version of ASpace (not the 2.0.0 RC2) and were too general to use. I just wanted to voice this to the community, in case others also have issues trying out the beta PUI or if anyone has any suggestions for implementing it. Thanks! Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From cspeterson at email.gwu.edu Tue Apr 18 08:57:02 2017 From: cspeterson at email.gwu.edu (Peterson, Christie) Date: Tue, 18 Apr 2017 08:57:02 -0400 Subject: [Archivesspace_Users_Group] Unable to edit archival object after transferring Message-ID: Hello, I'm having a problem with some archival objects where any attempt to edit them through the user interface results in the following error: translation missing: en.no key - translation missing: en.validation_errors.database_integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__duplicate_entry__297608 at archival_object-0__for_key__uniq_ao_pos_ The only thing I can think of that might be relevant is that these are objects in a series that was transferred from one collection to another via the interface. Has anyone run into this before? Have any suggestions? Thanks, Christie -- Christie S. Peterson University Archivist George Washington University Libraries 704H Gelman Library cspeterson at gwu.edu 202.994.3925 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ljdavis at jhu.edu Tue Apr 18 09:48:04 2017 From: ljdavis at jhu.edu (Lora Davis) Date: Tue, 18 Apr 2017 13:48:04 +0000 Subject: [Archivesspace_Users_Group] Unable to edit archival object after transferring In-Reply-To: References: Message-ID: <67399659-8C8E-40E4-910E-B8638D9ACC41@jhu.edu> Hey Christie, Given this: duplicate_entry__297608 at archival_object-0__for_key__uniq_ao_pos_ I?m thinking that what is going on is that during the merge you?ve ended up with two sets of archival_objects belonging to the same parent that have matching ?positions" (the ao field that tells ASpace where to place an object in the collection?s tree). If you have a way to look at the JSON for the archival objects you could confirm that multiple objects have the same position #. So, for example, archival_objects/2 would be: { "lock_version": 0, "position": 0, "publish": true, "ref_id": "9759e8ea59d8e8c95237974522c97551", "title": "Research Materials?, "parent": { "ref": "/repositories/2/archival_objects/1" } } And archival_objects/3 is also: { "lock_version": 0, "position": 0, "publish": true, "ref_id": "4b2114851f10f24ea86c6506fb1a829f", "title": "Rabelais-Villon", "parent": { "ref": "/repositories/2/archival_objects/1" } } That said, if this is the culprit, clearly this shouldn?t happen when transferring ao?s from one collection to another via the staff interface! Or, I could be way off base? :) Lora On Apr 18, 2017, at 8:57 AM, Peterson, Christie > wrote: Hello, I'm having a problem with some archival objects where any attempt to edit them through the user interface results in the following error: translation missing: en.no key - translation missing: en.validation_errors.database_integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__duplicate_entry__297608 at archival_object-0__for_key__uniq_ao_pos_ The only thing I can think of that might be relevant is that these are objects in a series that was transferred from one collection to another via the interface. Has anyone run into this before? Have any suggestions? Thanks, Christie -- Christie S. Peterson University Archivist George Washington University Libraries 704H Gelman Library cspeterson at gwu.edu 202.994.3925 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From cspeterson at email.gwu.edu Tue Apr 18 10:16:05 2017 From: cspeterson at email.gwu.edu (Peterson, Christie) Date: Tue, 18 Apr 2017 10:16:05 -0400 Subject: [Archivesspace_Users_Group] Unable to edit archival object after transferring In-Reply-To: <67399659-8C8E-40E4-910E-B8638D9ACC41@jhu.edu> References: <67399659-8C8E-40E4-910E-B8638D9ACC41@jhu.edu> Message-ID: Thanks, yeah, that's what I thought might have happened. Was wondering if anyone else had encountered it and if there was a known fix, since the transfer was done months ago and rolling back the db is not an option at this point. On Tue, Apr 18, 2017 at 9:48 AM, Lora Davis wrote: > Hey Christie, > > Given this: > > duplicate_entry__297608 at archival_object-0__for_key__uniq_ao_pos_ > > > I?m thinking that what is going on is that during the merge you?ve ended > up with two sets of archival_objects belonging to the same parent that have > matching ?positions" (the ao field that tells ASpace where to place an > object in the collection?s tree). If you have a way to look at the JSON > for the archival objects you could confirm that multiple objects have the > same position #. > > So, for example, archival_objects/2 would be: > > { > "lock_version": 0, > "position": 0, > "publish": true, > "ref_id": "9759e8ea59d8e8c95237974522c97551", > "title": "Research Materials?, > > "parent": { > "ref": "/repositories/2/archival_objects/1" > } > } > > And archival_objects/3 is also: > > { > "lock_version": 0, > "position": 0, > "publish": true, > "ref_id": "4b2114851f10f24ea86c6506fb1a829f", > "title": "Rabelais-Villon", > > "parent": { > "ref": "/repositories/2/archival_objects/1" > } > } > > That said, if this is the culprit, clearly this shouldn?t happen when > transferring ao?s from one collection to another via the staff interface! > > Or, I could be way off base? :) > > Lora > > > On Apr 18, 2017, at 8:57 AM, Peterson, Christie > wrote: > > Hello, > > I'm having a problem with some archival objects where any attempt to edit > them through the user interface results in the following error: > > translation missing: en.no key - translation missing: > en.validation_errors.database_integrity_constraint_conflict__java__ > commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolat > ionexception__duplicate_entry__297608 at archival_object-0__ > for_key__uniq_ao_pos_ > > The only thing I can think of that might be relevant is that these are > objects in a series that was transferred from one collection to another via > the interface. > > Has anyone run into this before? Have any suggestions? > > Thanks, > > Christie > > -- > Christie S. Peterson > > University Archivist > George Washington University Libraries > 704H Gelman Library > cspeterson at gwu.edu > 202.994.3925 <(202)%20994-3925> > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Christie S. Peterson University Archivist George Washington University Libraries 704H Gelman Library cspeterson at gwu.edu 202.994.3925 -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Tue Apr 18 10:43:04 2017 From: noah.huffman at duke.edu (Noah Huffman) Date: Tue, 18 Apr 2017 14:43:04 +0000 Subject: [Archivesspace_Users_Group] Unable to edit archival object after transferring In-Reply-To: References: <67399659-8C8E-40E4-910E-B8638D9ACC41@jhu.edu> Message-ID: Hi Christie, You can resequence your entire database on startup to solve the problem. Or, you can install this plugin and resequence just the offending resource record: https://github.com/archivesspace-plugins/resync You can read the long history of this issue in JIRA: https://archivesspace.atlassian.net/browse/AR-1326 -Noah From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Peterson, Christie Sent: Tuesday, April 18, 2017 10:16 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Unable to edit archival object after transferring Thanks, yeah, that's what I thought might have happened. Was wondering if anyone else had encountered it and if there was a known fix, since the transfer was done months ago and rolling back the db is not an option at this point. On Tue, Apr 18, 2017 at 9:48 AM, Lora Davis > wrote: Hey Christie, Given this: duplicate_entry__297608 at archival_object-0__for_key__uniq_ao_pos_ I?m thinking that what is going on is that during the merge you?ve ended up with two sets of archival_objects belonging to the same parent that have matching ?positions" (the ao field that tells ASpace where to place an object in the collection?s tree). If you have a way to look at the JSON for the archival objects you could confirm that multiple objects have the same position #. So, for example, archival_objects/2 would be: { "lock_version": 0, "position": 0, "publish": true, "ref_id": "9759e8ea59d8e8c95237974522c97551", "title": "Research Materials?, "parent": { "ref": "/repositories/2/archival_objects/1" } } And archival_objects/3 is also: { "lock_version": 0, "position": 0, "publish": true, "ref_id": "4b2114851f10f24ea86c6506fb1a829f", "title": "Rabelais-Villon", "parent": { "ref": "/repositories/2/archival_objects/1" } } That said, if this is the culprit, clearly this shouldn?t happen when transferring ao?s from one collection to another via the staff interface! Or, I could be way off base? :) Lora On Apr 18, 2017, at 8:57 AM, Peterson, Christie > wrote: Hello, I'm having a problem with some archival objects where any attempt to edit them through the user interface results in the following error: translation missing: en.no key - translation missing: en.validation_errors.database_integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__duplicate_entry__297608 at archival_object-0__for_key__uniq_ao_pos_ The only thing I can think of that might be relevant is that these are objects in a series that was transferred from one collection to another via the interface. Has anyone run into this before? Have any suggestions? Thanks, Christie -- Christie S. Peterson University Archivist George Washington University Libraries 704H Gelman Library cspeterson at gwu.edu 202.994.3925 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Christie S. Peterson University Archivist George Washington University Libraries 704H Gelman Library cspeterson at gwu.edu 202.994.3925 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cspeterson at email.gwu.edu Tue Apr 18 10:44:19 2017 From: cspeterson at email.gwu.edu (Peterson, Christie) Date: Tue, 18 Apr 2017 10:44:19 -0400 Subject: [Archivesspace_Users_Group] Unable to edit archival object after transferring In-Reply-To: References: <67399659-8C8E-40E4-910E-B8638D9ACC41@jhu.edu> Message-ID: Thank you so much, Noah! I thought there was an answer like this out there. Christie On Tue, Apr 18, 2017 at 10:43 AM, Noah Huffman wrote: > Hi Christie, > > > > You can resequence your entire database on startup to solve the problem. > Or, you can install this plugin and resequence just the offending resource > record: https://github.com/archivesspace-plugins/resync > > > > You can read the long history of this issue in JIRA: > https://archivesspace.atlassian.net/browse/AR-1326 > > > > -Noah > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Peterson, > Christie > *Sent:* Tuesday, April 18, 2017 10:16 AM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Unable to edit archival object > after transferring > > > > Thanks, yeah, that's what I thought might have happened. Was wondering if > anyone else had encountered it and if there was a known fix, since the > transfer was done months ago and rolling back the db is not an option at > this point. > > > > On Tue, Apr 18, 2017 at 9:48 AM, Lora Davis wrote: > > Hey Christie, > > > > Given this: > > > > duplicate_entry__297608 at archival_object-0__for_key__uniq_ao_pos_ > > > > I?m thinking that what is going on is that during the merge you?ve ended > up with two sets of archival_objects belonging to the same parent that have > matching ?positions" (the ao field that tells ASpace where to place an > object in the collection?s tree). If you have a way to look at the JSON > for the archival objects you could confirm that multiple objects have the > same position #. > > > > So, for example, archival_objects/2 would be: > > > > { > > "lock_version": 0, > > "position": 0, > > "publish": true, > > "ref_id": "9759e8ea59d8e8c95237974522c97551", > > "title": "Research Materials?, > > > > "parent": { > > "ref": "/repositories/2/archival_objects/1" > > } > > } > > > > And archival_objects/3 is also: > > > > { > > "lock_version": 0, > > "position": 0, > > "publish": true, > > "ref_id": "4b2114851f10f24ea86c6506fb1a829f", > > "title": "Rabelais-Villon", > > > > "parent": { > > "ref": "/repositories/2/archival_objects/1" > > } > > } > > > > That said, if this is the culprit, clearly this shouldn?t happen when > transferring ao?s from one collection to another via the staff interface! > > > > Or, I could be way off base? :) > > > > Lora > > > > > > On Apr 18, 2017, at 8:57 AM, Peterson, Christie > wrote: > > > > Hello, > > > > I'm having a problem with some archival objects where any attempt to edit > them through the user interface results in the following error: > > > > translation missing: en.no > > key - translation missing: en.validation_errors.database_ > integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__ > mysqlintegrityconstraintviolationexception__duplicate_entry_ > _297608 at archival_object-0__for_key__uniq_ao_pos_ > > > > The only thing I can think of that might be relevant is that these are > objects in a series that was transferred from one collection to another via > the interface. > > > > Has anyone run into this before? Have any suggestions? > > > > Thanks, > > > > Christie > > > > -- > > Christie S. Peterson > > > > University Archivist > > George Washington University Libraries > > 704H Gelman Library > > cspeterson at gwu.edu > > 202.994.3925 <(202)%20994-3925> > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > > > -- > > Christie S. Peterson > > > > University Archivist > > George Washington University Libraries > > 704H Gelman Library > > cspeterson at gwu.edu > > 202.994.3925 <(202)%20994-3925> > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Christie S. Peterson University Archivist George Washington University Libraries 704H Gelman Library cspeterson at gwu.edu 202.994.3925 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jteitelbaum at pabmc.net Tue Apr 18 10:55:14 2017 From: jteitelbaum at pabmc.net (Teitelbaum, Jesse) Date: Tue, 18 Apr 2017 10:55:14 -0400 Subject: [Archivesspace_Users_Group] Components out of order Message-ID: Is there an easy way to fix how AS prioritizes the components on a finding aid? On the staff interface, the components are in order of how they were entered (e.g. folder 1, folder 2, etc.). But when printed to PDF, the components are then ordered by title of each folder, instead of folder #. Also, is there a way to print an entire finding aid from the public interface? Jesse Teitelbaum | Associate Archivist Pennsylvania House of Representatives | Archives 469 Forum Building | Harrisburg PA 17120 Phone: 717.783.3866 | Fax: 717.772.1233 Email: jteitelbaum at pabmc.net www.house.state.pa.us/BMC/archives -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Apr 19 10:05:36 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 19 Apr 2017 14:05:36 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v2.0.0 released Message-ID: The ArchivesSpace team is very pleased to release version 2.0.0! ArchivesSpace 2.0.0 features work from our development partner, Hudson Molonglo (HM), as well as code contributions from community members Steve Majewski and Brother Paul of Abbaye de La Trappe, who has provided our first publicly shared French translations of the interface. Thanks to all who contributed, participated in testing the release candidates, and provided the feedback that led to the many improvements in this release. You can download the new release from Github at https://github.com/archivesspace/archivesspace/releases/tag/v2.0.0. Version 2.0.0 of ArchivesSpace is a major release, with many changes to the underlying technologies of the application as well as improved functionality in some key areas. Summary information about these changes is available in the release notes. The changes include upgrading to Rails 5, better performance for background jobs and larger databases, a new way to reorder components in resources and digital objects, and remediation of some issues with reports. The reports have not been completely reworked, but we have removed Jasper reports and replaced it with an internal report framework to make running reports more successful. We are continuing to work with the reports sub-team on improving the data that is output. We hope to put out minor releases with additional report fixes between now and the June 2017 release. * Please see the release page for a listing of all the new features and bug fixes included in this release. * Please see the technical documentation for information on how to upgrade your ArchivesSpace installations. By default, ArchivesSpace 2.0.0 uses the current public interface. We have provided two options for those who want to try out the beta public interface. We have a separate download called PUBLIC-BETA that comes with the new PUI enabled (https://github.com/archivesspace/archivesspace/releases/tag/PUBLIC-BETA). You will need to set an environmental variable for ASPACE_PUBLIC_NEW=true before starting up. You also can build from the regular 2.0.0 source after setting an environmental variable for ASPACE_PUBLIC_NEW=true. The beta public interface should not be used in production. Even though the new public interface is not yet ready for production use, if you are using the current public interface, you will notice some small changes brought in from the code from the beta public interface that will improve the experience. The new tree view for resources and digital objects shows the entire list of components, with the current component being highlighted. Also, a much larger set of EAD tags are now converted to HTML in both the current and the new PUI, allowing for better rendering than before of certain types of tagging. Please let us know if you have questions or encounter problems executing the upgrade. The next major release of ArchivesSpace is expected to be available in June. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 4144 bytes Desc: image002.jpg URL: From lsaegert at tsl.texas.gov Wed Apr 19 10:07:38 2017 From: lsaegert at tsl.texas.gov (Laura Saegert) Date: Wed, 19 Apr 2017 14:07:38 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v2.0.0 released In-Reply-To: References: Message-ID: Sorry for the message I just sent From: archivesspace_member_reps-bounces at lyralists.lyrasis.org [mailto:archivesspace_member_reps-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Wednesday, April 19, 2017 9:06 AM To: Archivesspace Users Group; Archivesspace Member Reps; archivesspace_tac_uac at lyralists.lyrasis.org Cc: ArchivesSpace Board of Trustees mail list Subject: [Archivesspace_member_reps] ArchivesSpace v2.0.0 released The ArchivesSpace team is very pleased to release version 2.0.0! ArchivesSpace 2.0.0 features work from our development partner, Hudson Molonglo (HM), as well as code contributions from community members Steve Majewski and Brother Paul of Abbaye de La Trappe, who has provided our first publicly shared French translations of the interface. Thanks to all who contributed, participated in testing the release candidates, and provided the feedback that led to the many improvements in this release. You can download the new release from Github at https://github.com/archivesspace/archivesspace/releases/tag/v2.0.0. Version 2.0.0 of ArchivesSpace is a major release, with many changes to the underlying technologies of the application as well as improved functionality in some key areas. Summary information about these changes is available in the release notes. The changes include upgrading to Rails 5, better performance for background jobs and larger databases, a new way to reorder components in resources and digital objects, and remediation of some issues with reports. The reports have not been completely reworked, but we have removed Jasper reports and replaced it with an internal report framework to make running reports more successful. We are continuing to work with the reports sub-team on improving the data that is output. We hope to put out minor releases with additional report fixes between now and the June 2017 release. * Please see the release page for a listing of all the new features and bug fixes included in this release. * Please see the technical documentation for information on how to upgrade your ArchivesSpace installations. By default, ArchivesSpace 2.0.0 uses the current public interface. We have provided two options for those who want to try out the beta public interface. We have a separate download called PUBLIC-BETA that comes with the new PUI enabled (https://github.com/archivesspace/archivesspace/releases/tag/PUBLIC-BETA). You will need to set an environmental variable for ASPACE_PUBLIC_NEW=true before starting up. You also can build from the regular 2.0.0 source after setting an environmental variable for ASPACE_PUBLIC_NEW=true. The beta public interface should not be used in production. Even though the new public interface is not yet ready for production use, if you are using the current public interface, you will notice some small changes brought in from the code from the beta public interface that will improve the experience. The new tree view for resources and digital objects shows the entire list of components, with the current component being highlighted. Also, a much larger set of EAD tags are now converted to HTML in both the current and the new PUI, allowing for better rendering than before of certain types of tagging. Please let us know if you have questions or encounter problems executing the upgrade. The next major release of ArchivesSpace is expected to be available in June. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: From Kevin.Clair at du.edu Thu Apr 20 10:50:12 2017 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 20 Apr 2017 14:50:12 +0000 Subject: [Archivesspace_Users_Group] overriding javascript via plugin Message-ID: Hello, I'm wondering if anyone on the list has managed to write a plugin to override Javascript functions in the ArchivesSpace frontend. Here at Denver our preference is to display component IDs in the resource tree view instead of Top Container information (see attached screenshot). Currently we do this through our local plugins [1], but since it looks like v2.0.0 moves all of that functionality into the script at https://github.com/archivesspace/archivesspace/blob/master/frontend/app/assets/javascripts/tree_renderers.js.erb, I can't figure out a way to customize the tree rendering to override the default behavior. There will likely be local resistance to upgrading if we lose this display customization, so any help with this would be appreciated. thanks! -k [1] https://github.com/duspeccoll/plugins_local/blob/master/frontend/views/shared/_tree.html.erb -------------- next part -------------- An HTML attachment was scrubbed... URL: From oallen at tacomacc.edu Thu Apr 20 18:40:01 2017 From: oallen at tacomacc.edu (Allen, Odette) Date: Thu, 20 Apr 2017 22:40:01 +0000 Subject: [Archivesspace_Users_Group] Nuanced JAVA calibration for AS setup at small institutions Message-ID: Hello All- So I am at a very small community college and trying to set AS set up. In seeking the support of my IT department where has been much protest (rending of shirts, pulling of hair) at the amount of JAVA knowledge required to calibrate AS into production mode. We don't have a JAVA specialist and I don't have the skillset, but I can't imagine this is a unique sitch. What are other small institutions with minimal tech supprt doing to run AS for production? Learning to code in JAVA? Does AS fly well enough without the tweaks in calibration? Odette Allen TCC Archive, Building 7 253-460-3990 -------------- next part -------------- An HTML attachment was scrubbed... URL: From megan at pnptc.org Thu Apr 20 18:57:49 2017 From: megan at pnptc.org (Megan Garbett-Styger) Date: Thu, 20 Apr 2017 15:57:49 -0700 Subject: [Archivesspace_Users_Group] Nuanced JAVA calibration for AS setup at small institutions In-Reply-To: References: Message-ID: Hi Odette, I am also without IT support. I ended up using this Youtube video to get me through set up and got it running successfully. https://www.youtube.com/watch?v=s8sDok-eMFo Best of luck! Megan On Thu, Apr 20, 2017 at 3:40 PM, Allen, Odette wrote: > Hello All- > > > > So I am at a very small community college and trying to set AS set up. In > seeking the support of my IT department where has been much protest > (rending of shirts, pulling of hair) at the amount of JAVA knowledge > required to calibrate AS into production mode. We don?t have a JAVA > specialist and I don?t have the skillset, but I can?t imagine this is a > unique sitch. What are other small institutions with minimal tech supprt > doing to run AS for production? Learning to code in JAVA? Does AS fly well > enough without the tweaks in calibration? > > > > Odette Allen > > TCC Archive, Building 7 > > 253-460-3990 <(253)%20460-3990> > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Megan Garbett-Styger Archivist Point No Point Treaty Council 19472 Powder Hill Place NE Suite 210 Poulsbo, WA 98370 360-297-6536 <360-297-6538> Direct 360-297-3413 Fax www.pnptc.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From jazairi at bc.edu Fri Apr 21 10:35:08 2017 From: jazairi at bc.edu (Adam Jazairi) Date: Fri, 21 Apr 2017 10:35:08 -0400 Subject: [Archivesspace_Users_Group] Nuanced JAVA calibration for AS setup at small institutions In-Reply-To: References: Message-ID: Hi Odette, I'm responsible for the technical upkeep of my institution's ArchivesSpace instance, and my lack of Java experience hasn't hindered our implementation efforts so far. You or your IT staff will probably need to adjust the Java virtual machine's resource consumption, but that doesn't require writing any code. There's some good documentation over here: http://archivesspace.github.io/archivesspace/user/tuning-archivesspace/ In my opinion, it's much more important to have some expertise in MySQL if you want to run AS in production. Ruby and JavaScript are necessary to write plugins, but that might not be a concern for your use case. (If you find that you do need a plugin, there's also a possibility that somebody else has already written it; AS users are great about sharing their work on GitHub.) Best, Adam On Thu, Apr 20, 2017 at 6:57 PM, Megan Garbett-Styger wrote: > Hi Odette, > I am also without IT support. I ended up using this Youtube video to get > me through set up and got it running successfully. > https://www.youtube.com/watch?v=s8sDok-eMFo > > Best of luck! > > Megan > > On Thu, Apr 20, 2017 at 3:40 PM, Allen, Odette > wrote: > >> Hello All- >> >> >> >> So I am at a very small community college and trying to set AS set up. In >> seeking the support of my IT department where has been much protest >> (rending of shirts, pulling of hair) at the amount of JAVA knowledge >> required to calibrate AS into production mode. We don?t have a JAVA >> specialist and I don?t have the skillset, but I can?t imagine this is a >> unique sitch. What are other small institutions with minimal tech supprt >> doing to run AS for production? Learning to code in JAVA? Does AS fly well >> enough without the tweaks in calibration? >> >> >> >> Odette Allen >> >> TCC Archive, Building 7 >> >> 253-460-3990 <(253)%20460-3990> >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Megan Garbett-Styger > Archivist > > Point No Point Treaty Council > 19472 Powder Hill Place NE Suite 210 > Poulsbo, WA 98370 > 360-297-6536 <360-297-6538> Direct > 360-297-3413 Fax > www.pnptc.org > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Adam Jazairi Digital Library Applications Developer Boston College Libraries (617) 552-1404 jazairi at bc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From lynn.moulton at bc.edu Fri Apr 21 10:47:53 2017 From: lynn.moulton at bc.edu (Lynn Moulton) Date: Fri, 21 Apr 2017 10:47:53 -0400 Subject: [Archivesspace_Users_Group] Manage Top Containers - searchable by resource identifier ? Message-ID: We're in the processing of migrating from Archivists Toolkit to ArchivesSpace and have pretty nearly worked out the kinks. However, I haven't figured out any way to set up the Manage Top Containers search or results so that they include the accession/resource Identifier. Using the full Identifier in either the Keywords or Accession/Resource fields in the Top Containers search yields no results. And when I search an accession by title, I can't tell the difference between accruals of related materials in the search results, as there is no column for the Identifier. The default settings for Browse>Resources also do not include the Identifier, but these can be modified in the User Preference Defaults menu. I couldn't find a similar option for Top Containers. Has anyone else run into this problem? Any solutions? Best, Lynn Moulton Processing Archivist Burns Library Boston College -------------- next part -------------- An HTML attachment was scrubbed... URL: From gpgaidmore at wm.edu Fri Apr 21 18:22:22 2017 From: gpgaidmore at wm.edu (Gaidmore, Gerald) Date: Fri, 21 Apr 2017 22:22:22 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Technical Advisory Council DEADLINE EXTENDED Message-ID: <2ad51d8187464ead84cc689ccf861db2@EXMBX02.campus.wm.edu> The ArchivesSpace Governance Board is seeking nominations for the ArchivesSpace Technical Advisory Council (TAC). Nominations may be made only by ArchivesSpace member representatives. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities assigned to TAC and who are capable of participating on a regular basis throughout the term of service of July 1, 2017-June 30, 2019. Self-nominations are also welcome. TAC Nominees do not need to be from ArchivesSpace Member Institutions. Nominations must be received by 9:00 p.m. EDT Monday, May 1. The Nominating Committee will review all nominations and recommend appointments to the Governance Board for approval. TAC (http://archivesspace.org/governance-board-and-councils/#TAC) is a critical part of the ArchivesSpace community, having responsibility for providing technical guidance to individuals or organizations contributing to application development, to the User Advisory Council, and to the ArchivesSpace Governance Board. TAC's current activities include: * developing a community of code committers, including helping to establish guidelines for contributing code and reviewing contributions, * reviewing enhancements and priorities, and testing in collaboration with the User Advisory Council, * providing support for migrating data to ArchivesSpace from other systems and support for importing and exporting data such as EAD, MARCXML, CSV * documenting and assisting with resolving bugs identified in the application, * identifying integration points for ArchivesSpace with other systems (e.g. digital asset management systems, patron and request management systems, etc.), creating resources to assist the community with integration work and, for specific integrations, developing technical requirements, and * updating technical documentation. Sub-teams will be established within TAC to address the areas identified above, as well other activity areas identified subsequently. Nominees must have sufficient knowledge of software development processes, architectures and/or coding practices to participate in and lead some of the identified activities. Nominees with experience in open source projects, developing web applications (particularly using Ruby on Rails and Sinatra), software testing, or interest in those areas, are especially welcome. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service for these appointments will be July 1, 2017-June 30, 2019. We expect to make up to 7 appointments, and each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2019-June 30, 2021. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicating the areas of activity to which the nominee is prepared to contribute. Again, self-nominations are also welcome. Return the completed form via email to the ArchivesSpace Program Manager, Christine Di Bella (christine.dibella at lyrasis.org), who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Monday, May 1. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, Jay Gaidmore The College of William & Mary Chair, and Governance Board member On behalf of Nominating Committee members: Gordon Daines, Brigham Young University, Chair of User Advisory Council Sally Vermaaten, Gates Archive, Chair of Technical Advisory Council Johna Von Behrens, University of Louisiana Lafayette, representing Very Large membership level Cyndi Shein, UNLV, representing Large membership level Mary Saffell, Texas Christian University, representing Medium membership level Julia Novakovic, The Strong National Museum of Play, representing Small membership level Annie Tummino, SUNY Maritime, representing Very Small membership level Christine Di Bella, ArchivesSpace Program Manager, ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Managing/endorsing/eliciting code contributions ___Application testing ___Migration issues, including import/exports and API design and implementation ___Bug fixes ___Program architecture and integrations with other software ___Technical documentation -------------- next part -------------- An HTML attachment was scrubbed... URL: From gpgaidmore at wm.edu Fri Apr 21 18:22:32 2017 From: gpgaidmore at wm.edu (Gaidmore, Gerald) Date: Fri, 21 Apr 2017 22:22:32 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Governance Board DEADLINE EXTENDED Message-ID: As chair of the 2017/18 ArchivesSpace Nominating Committee, I am writing to seek your nominations of candidates to stand for election for the ArchivesSpace Governance Board (http://archivesspace.org/governance-board-and-councils/#GovernanceBoard) - representing the Large, Medium, and Very Small membership levels. Member engagement is critical to the success of ArchivesSpace, and the Board relies upon your recommendations for strong candidates. Even if you represent a different category of membership, please consider colleagues you know at other institutions. Only ArchivesSpace Member Representatives may submit nominations. All other staff of ArchivesSpace member organizations must submit nominations through their Member Representative. All Member Representatives are strongly encouraged to consult with all interested colleagues within their organization to solicit recommendations for nominees. Self-nominations are also welcome if you represent a Large, Medium, or Very Small member institution. To submit nominations, send the name and institutional affiliation for each person, and indicate whether or not you have contacted the nominee. A member of the Nominating Committee will follow up with the nominee accordingly to confirm their interest. Self-nominees can simply indicate their interest. Nominees who confirm their interest in standing for election will be requested to supply a formal candidate statement outlining their qualifications for serving on the Governance Board. Nominations must be received by 9:00 p.m. EDT Monday, May 1. They should be sent to ArchivesSpace Program Manager Christine Di Bella (christine.dibella at lyrasis.org), who will collect nominations on behalf of the Nominating Committee. The Nominating Committee will review all nominations and confirm a slate of nominees with the current Governance Board. An election ballot will be circulated to member institutions in mid-May. The current incumbents at the Large and Very Small membership levels are eligible for re-election as representatives to the Governance Board. The current incumbent at the Medium membership level is no longer eligible for appointment. The terms for their successors will be July 1, 2017-June 30, 2019. Each newly elected member representative will be eligible to run for a second term, July 1, 2019-June 30, 2021. Nominees must be currently employed by an ArchivesSpace member organization in either the Large, Medium, and Very Small member levels (see the member lists at: http://archivesspace.org/community/whos-using-archivesspace/). Nominees should have administrative and fiscal oversight experience, characteristics typical of director or associate director level staff. The Governance Board is charged with providing oversight for the ArchivesSpace application and community, including fiscal oversight, the approval of development priorities, and oversight of the Technical and User Advisory councils. To meet the needs of a broad and diverse membership in a balanced and equitable way, the Governance Board is composed of twelve members, including: 9 voting members: 5 elected members, one from each of the five membership categories; 3 standing members, one representing each of the three original project partners (New York University, UC San Diego, and the University of Illinois, Urbana-Champaign); and 1 member representing the LYRASIS management team. 3 ex officio members: ArchivesSpace Program Manager, LYRASIS Director of Collection Services and Community Supported Software, and 1 member of the LYRASIS Board of Directors. Please feel free to contact me or any member of our Nominating Committee with any questions. Again, nominations should be sent to ArchivesSpace Program Manager Christine Di Bella (christine.dibella at lyrasis.org). All nominations must be received by 9:00 p.m. EDT Monday, May 1. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, Jay Gaidmore The College of William & Mary Chair, and Governance Board member On behalf of Nominating Committee members: Gordon Daines, Brigham Young University, Chair of User Advisory Council Sally Vermaaten, Gates Archive, Chair of Technical Advisory Council Johna Von Behrens, University of Louisiana Lafayette, representing Very Large membership level Cyndi Shein, UNLV, representing Large membership level Mary Saffell, Texas Christian University, representing Medium membership level Julia Novakovic, The Strong National Museum of Play, representing Small membership level Annie Tummino, SUNY Maritime, representing Very Small membership level Christine Di Bella, ArchivesSpace Program Manager, ex officio -------------- next part -------------- An HTML attachment was scrubbed... URL: From gpgaidmore at wm.edu Fri Apr 21 18:21:59 2017 From: gpgaidmore at wm.edu (Gaidmore, Gerald) Date: Fri, 21 Apr 2017 22:21:59 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace User Advisory Council DEADLINE EXTENDED Message-ID: <9245556f9de44236afbe22ff7065862d@EXMBX02.campus.wm.edu> The ArchivesSpace Governance Board is seeking nominations to fill up to 4 vacancies on the ArchivesSpace User Advisory Council (UAC). Nominees should be presently employed at an ArchivesSpace member institution in the Large, Medium, or Very Small levels (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). Nominations may be made only by ArchivesSpace Member Representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member Representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities projected for UAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Monday, May 1. The Nominations Committee will review all nominations and recommend appointments to the Governance Board for approval. UAC (http://archivesspace.org/governance-board-and-councils/#UAC) is a critical part of the ArchivesSpace community, serving as a communication conduit between ArchivesSpace governance groups and ArchivesSpace users. It is also the group that implements and contributes to ArchivesSpace user services. Some of the activities UAC is currently engaged in are: * soliciting, suggesting, and gathering requirements for enhancements to the ArchivesSpace application; * developing functional specifications for reports with the application; * reviewing enhancements and priorities, and testing in collaboration with the Technical Advisory Council; * maintaining and updating user documentation, as needed, of the ArchivesSpace application. Sub-teams will be established within UAC to address the areas identified above, as well as other activities identified subsequently. Nominees will be appointed to UAC according to their ability to participate in and lead some of the activities mentioned above. To nominate a candidate for the ArchivesSpace User Advisory Council, please identify the person and her/his organization in the form below, indicate the areas of activity to which the nominee is prepared to contribute. Again, self-nominations are also welcome. Return the completed form via email to ArchivesSpace Program Manager, Christine Di Bella (christine.dibella at lyrasis.org), who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Monday, May 1. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service will be July 1, 2017-June 30, 2019. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2019-June 30, 2021. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, Jay Gaidmore The College of William & Mary Chair, and Governance Board member On behalf of Nominating Committee members: Gordon Daines, Brigham Young University, Chair of User Advisory Council Sally Vermaaten, Gates Archive, Chair of Technical Advisory Council Johna Von Behrens, University of Louisiana Lafayette, representing Very Large membership level Cyndi Shein, UNLV, representing Large membership level Mary Saffell, Texas Christian University, representing Medium membership level Julia Novakovic, The Strong National Museum of Play, representing Small membership level Annie Tummino, SUNY Maritime, representing Very Small membership level Christine Di Bella, ArchivesSpace Program Manager, ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___New features, functional or technical specifications ___ Usability and quality assurance testing ___User/Help support ___Documentation -------------- next part -------------- An HTML attachment was scrubbed... URL: From Grant.Buttars at ed.ac.uk Mon Apr 24 07:36:30 2017 From: Grant.Buttars at ed.ac.uk (BUTTARS Grant) Date: Mon, 24 Apr 2017 11:36:30 +0000 Subject: [Archivesspace_Users_Group] Digital Object csv import: multiple file versions Message-ID: I'm currently working on importing digital object metadata and want to include more than one file version per object. The template only allows for one. Ideally, I'd also like to include external document links and notes (again none of these are in the template). Is there any way of achieving any of these? Many thanks Grant --------------------------------- Grant E. L. Buttars, | Deputy University Archivist | Special Collections | Centre for Research Collections | Division of Library and University Collections | University of Edinburgh George Square, Edinburgh | EH8 9LJ | http://www.ed.ac.uk/is/crc | tel: 0131 650 8379 | direct dial: 0131 651 3852 ================================= Coming to consult something? Please see http://www.ed.ac.uk/is/crc for service information Follow CRC [FaceBook-icon2][Twitter-icon2] Facebook: https://www.facebook.com/crc.edinburgh Twitter: https://twitter.com/CRC_EdUni Follow Archives [Twitter-icon2][Flickr-icon2][wordpress] Twitter: https://twitter.com/euarchives Flickr: http://www.flickr.com/photos/edinburgh-university-archives Blog: http://libraryblogs.is.ed.ac.uk/edinburghuniversityarchives Follow me professionally [Twitter-icon2][linkedin] Twitter: https://twitter.com/ButtarsGrant LinkedIn: https://www.linkedin.com/pub/grant-buttars/61/7b3/a09 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 1176 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 1147 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 1287 bytes Desc: image003.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 4228 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 2587 bytes Desc: image005.png URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: not available URL: From sdm7g at eservices.virginia.edu Mon Apr 24 12:11:28 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 24 Apr 2017 16:11:28 +0000 Subject: [Archivesspace_Users_Group] Digital Object csv import: multiple file versions In-Reply-To: References: Message-ID: <905C1D46-E7B5-4BFA-949A-918889EA3EAC@eservices.virginia.edu> I don?t believe you can do it with the CSV import. EAD import will treat multiple within as multiple file versions to one digital object. ( If you already have the resource those digital objects should be bound to in ArchivesSpace, there may be some cases where the easiest(*) thing to do is to export the object to EAD, add the digital objects to the appropriate components with a XSLT stylesheet, delete resource and reimport modified EAD in ArchivesSpace. ) The other alternative is to script something using the backend API. ( We?re testing using the API to connect our digitization tracking system to ArchiveSpace: tracking system keeps a link to ASpace archival_object, attaches an external_id in ASpace pointing back to tracking system item, and creates a digital_object attached to archival_object with URI to IIIF manifest. ) [ (*) ?easiest? only if XSLT transforms of EAD is what you are already used to doing. ] ? Steve M. On Apr 24, 2017, at 7:36 AM, BUTTARS Grant > wrote: I?m currently working on importing digital object metadata and want to include more than one file version per object. The template only allows for one. Ideally, I?d also like to include external document links and notes (again none of these are in the template). Is there any way of achieving any of these? Many thanks Grant -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at eservices.virginia.edu Mon Apr 24 14:24:14 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 24 Apr 2017 18:24:14 +0000 Subject: [Archivesspace_Users_Group] RFC: EAD import/export: mapping multiple unitid's and external-id's Message-ID: Request for comments: I?m testing a patch relating to these JIRA tickets: [AS-99] As an archivist, I would like to associate multiple identifiers with resources/objects and export it in EAD - JIRA [AR-1542] As an archivist, I would like to associate multiple identifiers with resources/objects and export it in EAD - JIRA [AR-1268] Need ability to parse the unitid for multiple values on EAD import - JIRA I?ve noticed that when there are multiple ?s in EAD, the last one overwrites previous ones so the last value is the one imported. In our cases, if there are multiple ?s, the first one is always the primary one. Other identifiers may into other systems may be added after the primary one. I would expect this to be the natural order ? does this conflict with anyone else?s experience ? ( Does anyone *want* the last value to override initial value? ) I propose changing this to make the first unitid the primary one on import. The other changes import additional ?s as external_ids IF they have a @type attribute. @type will be mapped to external_id.source. On export, external_ids are exported as unitid with @type=external_id.source. ?s following the initial primary without a @type attribute are dropped. ( This could be changed, as I don?t believe external_id has any *required* attributes: In our use cases, it didn?t seem to make much sense to keep an external id without an indicator of what system it?s an id into. ) I also note that AppConfig[:show_external_ids] is false by default. Is there a reason for this ? I believe that initially the external ids were mostly used for mapping conversions from Archon and AT. We have a strong need to link ArchivesSpace resources to resources in other systems. I would guess that this is a pretty widely shared requirement. ( Was hiding them a way of keeping users from editing them because Archon/AT migration depended on them ? ) Chasing this setting currently only makes existing external ids viewable and editable. I think it also makes sense to make them more generally available. Currently, you can?t add an external id from the frontend if there isn?t one already. Any comments or objections ? ? Steve Majewski / UVA Alderman Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave_mayo at harvard.edu Mon Apr 24 15:55:02 2017 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Mon, 24 Apr 2017 19:55:02 +0000 Subject: [Archivesspace_Users_Group] RFC: EAD import/export: mapping multiple unitid's and external-id's In-Reply-To: References: Message-ID: <5424028F-DAAF-4755-8F32-C252FE1C5FAD@harvard.edu> +1, and also this is true of unittitles as well; unfortunately, there?s no proper representation of multiple titles as of yet, but at the very least, take-first would be better than take-last there as well. - Dave Mayo Digital Library Software Engineer Harvard University > HUIT > LTS > OSC Development Group From: on behalf of "Majewski, Steven Dennis (sdm7g)" Reply-To: Archivesspace Users Group Date: Monday, April 24, 2017 at 2:24 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] RFC: EAD import/export: mapping multiple unitid's and external-id's Request for comments: I?m testing a patch relating to these JIRA tickets: [AS-99] As an archivist, I would like to associate multiple identifiers with resources/objects and export it in EAD - JIRA [AR-1542] As an archivist, I would like to associate multiple identifiers with resources/objects and export it in EAD - JIRA [AR-1268] Need ability to parse the unitid for multiple values on EAD import - JIRA I?ve noticed that when there are multiple ?s in EAD, the last one overwrites previous ones so the last value is the one imported. In our cases, if there are multiple ?s, the first one is always the primary one. Other identifiers may into other systems may be added after the primary one. I would expect this to be the natural order ? does this conflict with anyone else?s experience ? ( Does anyone *want* the last value to override initial value? ) I propose changing this to make the first unitid the primary one on import. The other changes import additional ?s as external_ids IF they have a @type attribute. @type will be mapped to external_id.source. On export, external_ids are exported as unitid with @type=external_id.source. ?s following the initial primary without a @type attribute are dropped. ( This could be changed, as I don?t believe external_id has any *required* attributes: In our use cases, it didn?t seem to make much sense to keep an external id without an indicator of what system it?s an id into. ) I also note that AppConfig[:show_external_ids] is false by default. Is there a reason for this ? I believe that initially the external ids were mostly used for mapping conversions from Archon and AT. We have a strong need to link ArchivesSpace resources to resources in other systems. I would guess that this is a pretty widely shared requirement. ( Was hiding them a way of keeping users from editing them because Archon/AT migration depended on them ? ) Chasing this setting currently only makes existing external ids viewable and editable. I think it also makes sense to make them more generally available. Currently, you can?t add an external id from the frontend if there isn?t one already. Any comments or objections ? ? Steve Majewski / UVA Alderman Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkottman at ku.edu Mon Apr 24 17:28:01 2017 From: mkottman at ku.edu (Kottman, Miloche) Date: Mon, 24 Apr 2017 21:28:01 +0000 Subject: [Archivesspace_Users_Group] Manage Top Containers - searchable by resource identifier ? In-Reply-To: References: Message-ID: Lynn, We are able to use the ?Resource? search on the Manage Top Containers page to find records without any issues (version 1.5.2). We use the identifier when performing the search because it?s easier/shorter to type. The search results in the typeahead display the title of the resource record so we do have to know both elements to actually retrieve something. For example: [cid:image001.png at 01D2BD16.48C843E0] The identifier for Correspondence of Francis Pierce Fitzwilliam is RH MS 12 so ArchivesSpace brought up the correct result, you just have to know the title to recognize it. As for Accession records, since similar titles can be challenging in the related accession/related resource fields in addition to the search results in the Top Container search, we include the date of the addition as part of the title. For example: Nicodemus ? (Addition 2016-06-01) so that we can tell accruals apart. Hope this helps, --Miloche From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lynn Moulton Sent: Friday, April 21, 2017 9:48 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Manage Top Containers - searchable by resource identifier ? We're in the processing of migrating from Archivists Toolkit to ArchivesSpace and have pretty nearly worked out the kinks. However, I haven't figured out any way to set up the Manage Top Containers search or results so that they include the accession/resource Identifier. Using the full Identifier in either the Keywords or Accession/Resource fields in the Top Containers search yields no results. And when I search an accession by title, I can't tell the difference between accruals of related materials in the search results, as there is no column for the Identifier. The default settings for Browse>Resources also do not include the Identifier, but these can be modified in the User Preference Defaults menu. I couldn't find a similar option for Top Containers. Has anyone else run into this problem? Any solutions? Best, Lynn Moulton Processing Archivist Burns Library Boston College -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 51818 bytes Desc: image001.png URL: From christine.dibella at lyrasis.org Tue Apr 25 13:44:25 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 25 Apr 2017 17:44:25 +0000 Subject: [Archivesspace_Users_Group] FW: call for ArchivesSpace Member Forum 2017 speakers and topics Message-ID: Just a reminder that we're seeking speakers and topics for this year's ArchivesSpace Member Forum. Fully formed sessions are appreciated, of course, but the planning group is also very glad to work with people if you're only at the seed stage, or have a great idea but are unsure about who can speak about it. Looking forward to your ideas and suggestions, small or big! Christine From: Christine Di Bella Sent: Thursday, April 13, 2017 12:44 PM To: Archivesspace Users Group ; 'Archivesspace Member Reps' ; 'archivesspace_tac_uac at lyralists.lyrasis.org' Cc: 'ArchivesSpace Board of Trustees mail list' Subject: call for ArchivesSpace Member Forum 2017 speakers and topics Hello ArchivesSpace members, ArchivesSpace will be holding its third annual Member Forum on July 25, 2017, at Portland State University in Portland, Oregon. Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. More information on the developing program is on the ArchivesSpace wiki at https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2017. The planning group is looking for speakers to cover a range of topics. We've suggested a few on the wiki page, but anything related to ArchivesSpace is fair game. We're looking for speakers for the proposed topics, as well as suggestions for more topics you'd like to learn or talk about at the meeting in half-day workshops in the morning, and plenary (full group) sessions or small group sessions in the afternoon. Afternoon sessions may take any one of a number of formats, including panels, lightning rounds, and discussion groups. There is a short Google submission form available at https://goo.gl/WWrjQt; you can submit ideas or volunteer yourself to speak either via the form or by emailing me directly. Proposals, ideas, and suggestions received by May 5 will receive priority consideration so that we can get the program squared away as soon as possible. If you have any questions or other suggestions at this point, please just let me know. Registration for the Member Forum will open later this spring. Thanks in advance for your help in making this a great event! Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 4144 bytes Desc: image003.jpg URL: From sdm7g at eservices.virginia.edu Tue Apr 25 14:01:34 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 25 Apr 2017 18:01:34 +0000 Subject: [Archivesspace_Users_Group] overriding javascript via plugin In-Reply-To: References: Message-ID: <691FA747-A878-4468-936E-CAEB45C5EEC6@eservices.virginia.edu> Your screenshot was dropped from your email, so I don?t know exactly what you want, but you can monkey patch ResourceRenderer methods and change or decorate output with something like this in your plugins/local/frontend/views/layout_head_html.erb: <% if controller.controller_name == 'resources' %> <% end %> ( Strip out all of the console.log debugging after you get it to do what you want. ) In a different use case, for adding IIIF image viewers for digital objects, what I want to modify is not available until the digital object file versions accordion is expanded, so I had to bind the bootstrap event to the body and delegate the event to the accordion element: $('body').on( 'show.bs.collapse', '#digital_object_file_versions__accordion', 'data', function ($x) {...} ); ? Steve M. On Apr 20, 2017, at 10:50 AM, Kevin Clair > wrote: Hello, I?m wondering if anyone on the list has managed to write a plugin to override Javascript functions in the ArchivesSpace frontend. Here at Denver our preference is to display component IDs in the resource tree view instead of Top Container information (see attached screenshot). Currently we do this through our local plugins [1], but since it looks like v2.0.0 moves all of that functionality into the script at https://github.com/archivesspace/archivesspace/blob/master/frontend/app/assets/javascripts/tree_renderers.js.erb, I can?t figure out a way to customize the tree rendering to override the default behavior. There will likely be local resistance to upgrading if we lose this display customization, so any help with this would be appreciated. thanks! -k [1] https://github.com/duspeccoll/plugins_local/blob/master/frontend/views/shared/_tree.html.erb _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Daniel.Thacker at tamuk.edu Tue Apr 25 14:11:57 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Tue, 25 Apr 2017 18:11:57 +0000 Subject: [Archivesspace_Users_Group] View Published option is being redirected to localhost instead of our IP address Message-ID: The view published option does not take us to the public side. In the url it directs us to localhost. We have to manually put our IP address where the localhost was and then we can see what the public sees. Is there anyway to fix this? Thank you Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at eservices.virginia.edu Tue Apr 25 14:39:27 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 25 Apr 2017 18:39:27 +0000 Subject: [Archivesspace_Users_Group] View Published option is being redirected to localhost instead of our IP address In-Reply-To: References: Message-ID: <4F607F5C-F785-44D4-BF6A-A2824F92C872@eservices.virginia.edu> You need to change AppConfig[:public_proxy_url] in config.rb from default localhost to actual hostname: AppConfig[:frontend_url] = "http://localhost:8080" AppConfig[:frontend_proxy_url] = proc { AppConfig[:frontend_url] } AppConfig[:public_proxy_url] = proc { AppConfig[:public_url] } AppConfig[:public_url] = "http://localhost:8081" Not sure if there is a link back in the other direction ( public -> frontend ) but if there is you should also set :frontend_proxy_url We usually have frontend proxied thru Apache, so I used this as my default configs, so it works whether I?m on test or production servers, but this wouldn?t work if VHOST names for proxies were different from hostname: AppConfig[:hostname] = proc { Socket.gethostname } AppConfig[:frontend_proxy_url] = proc { "http://#{AppConfig[:hostname]}" } AppConfig[:public_proxy_url] = proc { "http://#{AppConfig[:hostname]}:8081" } ? Steve M. On Apr 25, 2017, at 2:11 PM, Daniel L Thacker > wrote: The view published option does not take us to the public side. In the url it directs us to localhost. We have to manually put our IP address where the localhost was and then we can see what the public sees. Is there anyway to fix this? Thank you Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Daniel.Thacker at tamuk.edu Tue Apr 25 15:17:16 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Tue, 25 Apr 2017 19:17:16 +0000 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Message-ID: I keep on getting a failed status on any kind of report I run. I've tried generating all the different types of reports you can export and our different repositories. One repository are records we hand typed in the other is a repository we successful migrated into. This particular report was for accessions record reports. Here is the log: Thank you. Generating report Error executing SQL statement for : accessionsRecord net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) java.lang.Thread.run(java/lang/Thread.java:745) Done. Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: From archives at mobarch.org Tue Apr 25 16:29:59 2017 From: archives at mobarch.org (Karen Horton) Date: Tue, 25 Apr 2017 20:29:59 +0000 Subject: [Archivesspace_Users_Group] Nuanced JAVA calibration for AS setup at small institutions In-Reply-To: References: Message-ID: <90df23c8399745f0848be2d2d1588f5c@AOM-Exch01.AOM.ORG> Odette, I am a lone arranger and probably worse off than you in the IT department. I was successful in installing and making AS work on my laptop way back when it was first released to the public, but the many upgrades finally did me in and I opted to have my instance hosted at LibraryHost, which is not too expensive and has worked out well for me. Perhaps you should consider such an arrangement with them or Lyrasis and possibly there are others who provide the service. I am finding it to be time consuming enough just to enter data into my hosted instance-I would never get anywhere if I were also responsible for the technical stuff :) Karen Horton, CA, Archivist Archdiocese of Mobile From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Allen, Odette Sent: Thursday, April 20, 2017 5:40 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Nuanced JAVA calibration for AS setup at small institutions Hello All- So I am at a very small community college and trying to set AS set up. In seeking the support of my IT department where has been much protest (rending of shirts, pulling of hair) at the amount of JAVA knowledge required to calibrate AS into production mode. We don't have a JAVA specialist and I don't have the skillset, but I can't imagine this is a unique sitch. What are other small institutions with minimal tech supprt doing to run AS for production? Learning to code in JAVA? Does AS fly well enough without the tweaks in calibration? Odette Allen TCC Archive, Building 7 253-460-3990 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Tue Apr 25 17:25:12 2017 From: mang.sun at rice.edu (Mang Sun) Date: Tue, 25 Apr 2017 16:25:12 -0500 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports In-Reply-To: References: Message-ID: <3a0cd73b-f695-2356-89ca-d22a1be18205@rice.edu> Make sure you have AS created User Defined functions (about 63 functions) present in the underlying MYSQL by running "show function status" under MySQL prompt. Mang Sun Rice U. On 4/25/2017 2:17 PM, Daniel L Thacker wrote: > > I keep on getting a failed status on any kind of report I run. I've > tried generating all the different types of reports you can export and > our different repositories. One repository are records we hand typed > in the other is a repository we successful migrated into. This > particular report was for accessions record reports. Here is the log: > Thank you. > > > > Generating report > Error executing SQL statement for : accessionsRecord > net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) > net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) > net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) > net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) > net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) > net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) > net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) > net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) > net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) > java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) > RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) > Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) > Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) > Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) > Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) > RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) > org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) > RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) > RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) > RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) > RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) > BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) > BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) > RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) > java.lang.Thread.run(java/lang/Thread.java:745) > Done. > > > Daniel Thacker > > Digital Archivist > > James C. Jernigan Library > > Texas A&M University-Kingsville > > MSC 197 > > 700 University Blvd > > Kingsville, TX 78363-8202 > > 361-593-4154 > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at dishevelled.net Wed Apr 26 01:41:05 2017 From: mark at dishevelled.net (Mark Triggs) Date: Wed, 26 Apr 2017 15:41:05 +1000 Subject: [Archivesspace_Users_Group] ArchivesSpace performance monitor plugin Message-ID: <874lxbsp3i.fsf@dishevelled.net> Hi all, Late last year I put together an ArchivesSpace plugin to catch some of the more common issues that we've seen affect ArchivesSpace's performance. While ArchivesSpace is running, the plugin monitors your system and database and logs information about anything unusual it finds. You can find it here: https://github.com/hudmol/system_performance_monitor To give an idea of the sorts of issues it looks for, it will tell you about: * opportunities for MySQL tuning (buffer pool sizing) * excessively high levels of network latency between the ArchivesSpace server and its database * running low on disk space * running out of JVM memory * running too few or too many indexer threads I've run this against ArchivesSpace 1.5.x and ArchivesSpace 2.0.0 for a few months now. Performance impact on the running system should be negligible in general. If you want to check for low hanging performance fruit--or just like being nagged--this could be the plugin for you! Cheers, Mark -- Mark Triggs -------------- next part -------------- An HTML attachment was scrubbed... URL: From flannon at nyu.edu Wed Apr 26 09:59:43 2017 From: flannon at nyu.edu (Flannon Jackson) Date: Wed, 26 Apr 2017 09:59:43 -0400 Subject: [Archivesspace_Users_Group] ArchivesSpace performance monitor plugin In-Reply-To: <874lxbsp3i.fsf@dishevelled.net> References: <874lxbsp3i.fsf@dishevelled.net> Message-ID: Very cool! We'll give it a try and see how it goes. -f On Wed, Apr 26, 2017 at 1:41 AM, Mark Triggs wrote: > Hi all, > > Late last year I put together an ArchivesSpace plugin to catch some of the > more common issues that we've seen affect ArchivesSpace's performance. > While ArchivesSpace is running, the plugin monitors your system and > database and logs information about anything unusual it finds. You can find > it here: > > https://github.com/hudmol/system_performance_monitor > > To give an idea of the sorts of issues it looks for, it will tell you > about: > > - > > opportunities for MySQL tuning (buffer pool sizing) > - > > excessively high levels of network latency between the ArchivesSpace > server and its database > - > > running low on disk space > - > > running out of JVM memory > - > > running too few or too many indexer threads > > I've run this against ArchivesSpace 1.5.x and ArchivesSpace 2.0.0 for a > few months now. Performance impact on the running system should be > negligible in general. If you want to check for low hanging performance > fruit--or just like being nagged--this could be the plugin for you! > > Cheers, > > Mark > > -- > Mark Triggs > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at eservices.virginia.edu Wed Apr 26 11:15:36 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 26 Apr 2017 15:15:36 +0000 Subject: [Archivesspace_Users_Group] RFC: EAD import/export: mapping multiple unitid's and external-id's In-Reply-To: <5424028F-DAAF-4755-8F32-C252FE1C5FAD@harvard.edu> References: <5424028F-DAAF-4755-8F32-C252FE1C5FAD@harvard.edu> Message-ID: <264DC8D7-10B0-40C9-9CBF-5259763D2578@eservices.virginia.edu> Would it make more sense to concatenate multiple unittitles ? I don?t think I?ve actually run into one in the wild. ? Steve M. On Apr 24, 2017, at 3:55 PM, Mayo, Dave > wrote: +1, and also this is true of unittitles as well; unfortunately, there?s no proper representation of multiple titles as of yet, but at the very least, take-first would be better than take-last there as well. - Dave Mayo Digital Library Software Engineer Harvard University > HUIT > LTS > OSC Development Group From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Monday, April 24, 2017 at 2:24 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] RFC: EAD import/export: mapping multiple unitid's and external-id's Request for comments: I?m testing a patch relating to these JIRA tickets: [AS-99] As an archivist, I would like to associate multiple identifiers with resources/objects and export it in EAD - JIRA [AR-1542] As an archivist, I would like to associate multiple identifiers with resources/objects and export it in EAD - JIRA [AR-1268] Need ability to parse the unitid for multiple values on EAD import - JIRA I?ve noticed that when there are multiple ?s in EAD, the last one overwrites previous ones so the last value is the one imported. In our cases, if there are multiple ?s, the first one is always the primary one. Other identifiers may into other systems may be added after the primary one. I would expect this to be the natural order ? does this conflict with anyone else?s experience ? ( Does anyone *want* the last value to override initial value? ) I propose changing this to make the first unitid the primary one on import. The other changes import additional ?s as external_ids IF they have a @type attribute. @type will be mapped to external_id.source. On export, external_ids are exported as unitid with @type=external_id.source. ?s following the initial primary without a @type attribute are dropped. ( This could be changed, as I don?t believe external_id has any *required* attributes: In our use cases, it didn?t seem to make much sense to keep an external id without an indicator of what system it?s an id into. ) I also note that AppConfig[:show_external_ids] is false by default. Is there a reason for this ? I believe that initially the external ids were mostly used for mapping conversions from Archon and AT. We have a strong need to link ArchivesSpace resources to resources in other systems. I would guess that this is a pretty widely shared requirement. ( Was hiding them a way of keeping users from editing them because Archon/AT migration depended on them ? ) Chasing this setting currently only makes existing external ids viewable and editable. I think it also makes sense to make them more generally available. Currently, you can?t add an external id from the frontend if there isn?t one already. Any comments or objections ? ? Steve Majewski / UVA Alderman Library _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Apr 26 11:18:09 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 26 Apr 2017 15:18:09 +0000 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports In-Reply-To: References: Message-ID: Dear Daniel, What version of ArchivesSpace are you running? There are some differences between different versions for what you need to do to run reports, and also which reports run successfully. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Tuesday, April 25, 2017 3:17 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports I keep on getting a failed status on any kind of report I run. I've tried generating all the different types of reports you can export and our different repositories. One repository are records we hand typed in the other is a repository we successful migrated into. This particular report was for accessions record reports. Here is the log: Thank you. Generating report Error executing SQL statement for : accessionsRecord net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) java.lang.Thread.run(java/lang/Thread.java:745) Done. Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 4144 bytes Desc: image003.jpg URL: From Daniel.Thacker at tamuk.edu Wed Apr 26 11:37:09 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Wed, 26 Apr 2017 15:37:09 +0000 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports In-Reply-To: References: , Message-ID: Hi Christine, We are running v1.5.4. I also got some advice to do: "Make sure you have AS created User Defined functions (about 63 functions) present in the underlying MYSQL by running "show function status" under MySQL prompt." So right now, I am heading over to our IT guys and see if they can "show function status" under MYSQL. Would you agree with this assessment? Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Christine Di Bella Sent: Wednesday, April 26, 2017 10:18:09 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Dear Daniel, What version of ArchivesSpace are you running? There are some differences between different versions for what you need to do to run reports, and also which reports run successfully. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Tuesday, April 25, 2017 3:17 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports I keep on getting a failed status on any kind of report I run. I've tried generating all the different types of reports you can export and our different repositories. One repository are records we hand typed in the other is a repository we successful migrated into. This particular report was for accessions record reports. Here is the log: Thank you. Generating report Error executing SQL statement for : accessionsRecord net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) java.lang.Thread.run(java/lang/Thread.java:745) Done. Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 4144 bytes Desc: image003.jpg URL: From dave_mayo at harvard.edu Wed Apr 26 12:29:23 2017 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Wed, 26 Apr 2017 16:29:23 +0000 Subject: [Archivesspace_Users_Group] RFC: EAD import/export: mapping multiple unitid's and external-id's In-Reply-To: <264DC8D7-10B0-40C9-9CBF-5259763D2578@eservices.virginia.edu> References: <5424028F-DAAF-4755-8F32-C252FE1C5FAD@harvard.edu>, <264DC8D7-10B0-40C9-9CBF-5259763D2578@eservices.virginia.edu> Message-ID: We did that as a preprocessing step, but one use of multiple unittitles would be works with primary titles in multiple languages, right? In which case dropping attributes matters. And what makes a good delimiter depends on the corpus - we used double-dagger, but other places might have EADs that include that character. So, anyway, my vote is that that can be a good local decision, but not a good "bake into the application" decision. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Wednesday, April 26, 2017 11:15:36 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] RFC: EAD import/export: mapping multiple unitid's and external-id's Would it make more sense to concatenate multiple unittitles ? I don?t think I?ve actually run into one in the wild. ? Steve M. On Apr 24, 2017, at 3:55 PM, Mayo, Dave > wrote: +1, and also this is true of unittitles as well; unfortunately, there?s no proper representation of multiple titles as of yet, but at the very least, take-first would be better than take-last there as well. - Dave Mayo Digital Library Software Engineer Harvard University > HUIT > LTS > OSC Development Group From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Monday, April 24, 2017 at 2:24 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] RFC: EAD import/export: mapping multiple unitid's and external-id's Request for comments: I?m testing a patch relating to these JIRA tickets: [AS-99] As an archivist, I would like to associate multiple identifiers with resources/objects and export it in EAD - JIRA [AR-1542] As an archivist, I would like to associate multiple identifiers with resources/objects and export it in EAD - JIRA [AR-1268] Need ability to parse the unitid for multiple values on EAD import - JIRA I?ve noticed that when there are multiple ?s in EAD, the last one overwrites previous ones so the last value is the one imported. In our cases, if there are multiple ?s, the first one is always the primary one. Other identifiers may into other systems may be added after the primary one. I would expect this to be the natural order ? does this conflict with anyone else?s experience ? ( Does anyone *want* the last value to override initial value? ) I propose changing this to make the first unitid the primary one on import. The other changes import additional ?s as external_ids IF they have a @type attribute. @type will be mapped to external_id.source. On export, external_ids are exported as unitid with @type=external_id.source. ?s following the initial primary without a @type attribute are dropped. ( This could be changed, as I don?t believe external_id has any *required* attributes: In our use cases, it didn?t seem to make much sense to keep an external id without an indicator of what system it?s an id into. ) I also note that AppConfig[:show_external_ids] is false by default. Is there a reason for this ? I believe that initially the external ids were mostly used for mapping conversions from Archon and AT. We have a strong need to link ArchivesSpace resources to resources in other systems. I would guess that this is a pretty widely shared requirement. ( Was hiding them a way of keeping users from editing them because Archon/AT migration depended on them ? ) Chasing this setting currently only makes existing external ids viewable and editable. I think it also makes sense to make them more generally available. Currently, you can?t add an external id from the frontend if there isn?t one already. Any comments or objections ? ? Steve Majewski / UVA Alderman Library _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at eservices.virginia.edu Wed Apr 26 12:48:54 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 26 Apr 2017 16:48:54 +0000 Subject: [Archivesspace_Users_Group] RFC: EAD import/export: mapping multiple unitid's and external-id's In-Reply-To: References: <5424028F-DAAF-4755-8F32-C252FE1C5FAD@harvard.edu> <264DC8D7-10B0-40C9-9CBF-5259763D2578@eservices.virginia.edu> Message-ID: <6F53148C-595E-44C0-9D21-118FE6F1A55F@eservices.virginia.edu> OK: That makes it sound like ?take-first? is the best general/global rule. Anything else would probably take special handling & local knowledge about what is intended by multiple titles. ? Steve. On Apr 26, 2017, at 12:29 PM, Mayo, Dave > wrote: We did that as a preprocessing step, but one use of multiple unittitles would be works with primary titles in multiple languages, right? In which case dropping attributes matters. And what makes a good delimiter depends on the corpus - we used double-dagger, but other places might have EADs that include that character. So, anyway, my vote is that that can be a good local decision, but not a good "bake into the application" decision. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Wednesday, April 26, 2017 11:15:36 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] RFC: EAD import/export: mapping multiple unitid's and external-id's Would it make more sense to concatenate multiple unittitles ? I don?t think I?ve actually run into one in the wild. ? Steve M. On Apr 24, 2017, at 3:55 PM, Mayo, Dave > wrote: +1, and also this is true of unittitles as well; unfortunately, there?s no proper representation of multiple titles as of yet, but at the very least, take-first would be better than take-last there as well. - Dave Mayo Digital Library Software Engineer Harvard University > HUIT > LTS > OSC Development Group From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Monday, April 24, 2017 at 2:24 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] RFC: EAD import/export: mapping multiple unitid's and external-id's Request for comments: I?m testing a patch relating to these JIRA tickets: [AS-99] As an archivist, I would like to associate multiple identifiers with resources/objects and export it in EAD - JIRA [AR-1542] As an archivist, I would like to associate multiple identifiers with resources/objects and export it in EAD - JIRA [AR-1268] Need ability to parse the unitid for multiple values on EAD import - JIRA I?ve noticed that when there are multiple ?s in EAD, the last one overwrites previous ones so the last value is the one imported. In our cases, if there are multiple ?s, the first one is always the primary one. Other identifiers may into other systems may be added after the primary one. I would expect this to be the natural order ? does this conflict with anyone else?s experience ? ( Does anyone *want* the last value to override initial value? ) I propose changing this to make the first unitid the primary one on import. The other changes import additional ?s as external_ids IF they have a @type attribute. @type will be mapped to external_id.source. On export, external_ids are exported as unitid with @type=external_id.source. ?s following the initial primary without a @type attribute are dropped. ( This could be changed, as I don?t believe external_id has any *required* attributes: In our use cases, it didn?t seem to make much sense to keep an external id without an indicator of what system it?s an id into. ) I also note that AppConfig[:show_external_ids] is false by default. Is there a reason for this ? I believe that initially the external ids were mostly used for mapping conversions from Archon and AT. We have a strong need to link ArchivesSpace resources to resources in other systems. I would guess that this is a pretty widely shared requirement. ( Was hiding them a way of keeping users from editing them because Archon/AT migration depended on them ? ) Chasing this setting currently only makes existing external ids viewable and editable. I think it also makes sense to make them more generally available. Currently, you can?t add an external id from the frontend if there isn?t one already. Any comments or objections ? ? Steve Majewski / UVA Alderman Library _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Apr 26 12:55:48 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 26 Apr 2017 16:55:48 +0000 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports In-Reply-To: References: , Message-ID: Hi Daniel, I'm not familiar with that being a reason for having problems with reports, but others may be able to help with that. What I can point you to is the information about enabling reports for versions through 1.5.4 in the user manual at https://docs.archivesspace.org/Default.htm#ReportsEnabling.htm. Jasper reports has been removed from the application starting with 2.0.0, so these steps will no longer be necessary in future upgrades. Reports are an area of the application that is under active development at this time and we hope to have more updates available soon. An alternate that some people are using with success is setting up an ODBC connection or otherwise hooking ArchivesSpace up to output data to an external program. As one example, Nancy Enneking of the Getty presented a lightning talk titled DIY Reports in ArchivesSpace at a session called Making ArchivesSpace Work for You at SAA last summer. Nancy's talk is in the file posted at http://schd.ws/hosted_files/archives2016/3e/Session501-All_presenters.pptx; Nancy's starts on page 40. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Wednesday, April 26, 2017 11:37 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Christine, We are running v1.5.4. I also got some advice to do: "Make sure you have AS created User Defined functions (about 63 functions) present in the underlying MYSQL by running "show function status" under MySQL prompt." So right now, I am heading over to our IT guys and see if they can "show function status" under MYSQL. Would you agree with this assessment? Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Wednesday, April 26, 2017 10:18:09 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Dear Daniel, What version of ArchivesSpace are you running? There are some differences between different versions for what you need to do to run reports, and also which reports run successfully. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Tuesday, April 25, 2017 3:17 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports I keep on getting a failed status on any kind of report I run. I've tried generating all the different types of reports you can export and our different repositories. One repository are records we hand typed in the other is a repository we successful migrated into. This particular report was for accessions record reports. Here is the log: Thank you. Generating report Error executing SQL statement for : accessionsRecord net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) java.lang.Thread.run(java/lang/Thread.java:745) Done. Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: From KennedyN at si.edu Thu Apr 27 05:42:01 2017 From: KennedyN at si.edu (Kennedy, Nancy) Date: Thu, 27 Apr 2017 09:42:01 +0000 Subject: [Archivesspace_Users_Group] Scope locations browse view to repository Message-ID: <4142170736420940ACB07EE9EECDC21F34DA4DB7@si-msedag04.US.SINET.SI.EDU> Morning, Is it possible to scope the browse list of locations to a specific repository? If I have Repo2 through Repo18, are there any configuration options so that a user in Repo6 will only see locations for that repository? In our environment, we have 15+ repositories, each with many locations. Several repositories have multiple buildings, so even the building facet list could be large. Facets help narrow by building, but users still appear to be browsing the entire set of thousands of locations, even if the locations are reserved for a specific repository. Holdings are only listed for the user's repository, of course, but I'm hoping to also avoid presenting all users, in all units, the full set of locations. Nancy Nancy Kennedy Smithsonian Institution kennedyn at si.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Thu Apr 27 11:10:27 2017 From: mang.sun at rice.edu (Mang Sun) Date: Thu, 27 Apr 2017 10:10:27 -0500 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports In-Reply-To: References: Message-ID: Daniel, What do you find with the said SQL command ? Mang On 4/26/2017 10:37 AM, Daniel L Thacker wrote: > > Hi Christine, > > > We are running v1.5.4. I also got some advice to do: > > > "Make sure you have AS created User Defined functions (about 63 > functions) present in the underlying MYSQL by running "show function > status" under MySQL prompt." > > > So right now, I am heading over to our IT guys and see if they can > "show function status" under MYSQL. Would you agree with this > assessment? > > > Thank you, > > > Daniel Thacker > > Digital Archivist > > James C. Jernigan Library > > Texas A&M University-Kingsville > > MSC 197 > > 700 University Blvd > > Kingsville, TX 78363-8202 > > 361-593-4154 > > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Christine Di Bella > *Sent:* Wednesday, April 26, 2017 10:18:09 AM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Keep getting Failed status > on generating reports > > Dear Daniel, > > What version of ArchivesSpace are you running? There are some > differences between different versions for what you need to do to run > reports, and also which reports run successfully. > > Christine > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 > > 678-235-2905 > > cdibella13 (Skype) > > ASpaceOrgHomeMedium > > *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] *On > Behalf Of *Daniel L Thacker > *Sent:* Tuesday, April 25, 2017 3:17 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Keep getting Failed status on > generating reports > > I keep on getting a failed status on any kind of report I run. I've > tried generating all the different types of reports you can export and > our different repositories. One repository are records we hand typed > in the other is a repository we successful migrated into. This > particular report was for accessions record reports. Here is the log: > Thank you. > > Generating report > > Error executing SQL statement for : accessionsRecord > > net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) > > net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) > > net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) > > net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) > > net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) > > net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) > > net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) > > net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) > > net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) > > java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) > > RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) > > Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) > > Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) > > Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) > > Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) > > RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) > > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) > > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) > > org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) > > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) > > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) > > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) > > DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) > > RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) > > RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) > > RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) > > RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) > > BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) > > BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) > > RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) > > java.lang.Thread.run(java/lang/Thread.java:745) > > Done. > > Daniel Thacker > > Digital Archivist > > James C. Jernigan Library > > Texas A&M University-Kingsville > > MSC 197 > > 700 University Blvd > > Kingsville, TX 78363-8202 > > 361-593-4154 > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 4144 bytes Desc: not available URL: From Daniel.Thacker at tamuk.edu Thu Apr 27 11:14:36 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Thu, 27 Apr 2017 15:14:36 +0000 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports In-Reply-To: References: Message-ID: Our IT guy said it didn't work for us. We are currently testing the new 2.0 version and hopefully we can run the reports we need like Accession Reports. We tried the the MYSQL solution for V1.5. Thank so much for following up with us. It is greatly appreciated. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun Sent: Thursday, April 27, 2017 10:10 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Daniel, What do you find with the said SQL command ? Mang On 4/26/2017 10:37 AM, Daniel L Thacker wrote: Hi Christine, We are running v1.5.4. I also got some advice to do: "Make sure you have AS created User Defined functions (about 63 functions) present in the underlying MYSQL by running "show function status" under MySQL prompt." So right now, I am heading over to our IT guys and see if they can "show function status" under MYSQL. Would you agree with this assessment? Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Christine Di Bella Sent: Wednesday, April 26, 2017 10:18:09 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Dear Daniel, What version of ArchivesSpace are you running? There are some differences between different versions for what you need to do to run reports, and also which reports run successfully. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Tuesday, April 25, 2017 3:17 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports I keep on getting a failed status on any kind of report I run. I've tried generating all the different types of reports you can export and our different repositories. One repository are records we hand typed in the other is a repository we successful migrated into. This particular report was for accessions record reports. Here is the log: Thank you. Generating report Error executing SQL statement for : accessionsRecord net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) java.lang.Thread.run(java/lang/Thread.java:745) Done. Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: From Daniel.Thacker at tamuk.edu Thu Apr 27 12:07:38 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Thu, 27 Apr 2017 16:07:38 +0000 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports In-Reply-To: References: , , Message-ID: We set up a test machine with V2.0 and followed the Manuel, the software works but still having problems with the reports. This was the failed status log: Follow Log Generating report Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: FUNCTION archivesspace.GetAccessionProcessed does not exist java.lang.reflect.Constructor.newInstance(java/lang/reflect/Constructor.java:423) com.mysql.jdbc.Util.handleNewInstance(com/mysql/jdbc/Util.java:425) com.mysql.jdbc.Util.getInstance(com/mysql/jdbc/Util.java:408) com.mysql.jdbc.SQLError.createSQLException(com/mysql/jdbc/SQLError.java:943) com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3973) com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3909) com.mysql.jdbc.MysqlIO.sendCommand(com/mysql/jdbc/MysqlIO.java:2527) com.mysql.jdbc.MysqlIO.sqlQueryDirect(com/mysql/jdbc/MysqlIO.java:2680) com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2497) com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2455) com.mysql.jdbc.StatementImpl.executeQuery(com/mysql/jdbc/StatementImpl.java:1369) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther1:executeQuery(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.logging.log_yield(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/logging.rb:33) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther8:log_yield(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.statement(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:646) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther25:statement(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther2:hold(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther35:synchronize(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther7:execute(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther2:execute(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.fetch_rows(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther7:fetch_rows(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:139) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.each(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:139) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther11:each(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:71) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.columns(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:71) RUBY.headers(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/abstract_report.rb:40) RUBY.each(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/csv_response.rb:10) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/csv_response.rb:20) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:27) RUBY.block in run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/reports_runner.rb:37) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in transaction(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions._transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.invokeOther14:_transaction(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.block in transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther2:hold(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.invokeOther35:synchronize(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther2:transaction(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.transaction(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther6:transaction(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:305) org.jruby.RubyFixnum$INVOKER$i$0$0$times.call(org/jruby/RubyFixnum$INVOKER$i$0$0$times.gen) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther50:times(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) org.jruby.RubyClass.finvoke(org/jruby/RubyClass.java:522) org.jruby.RubyBasicObject.send19(org/jruby/RubyBasicObject.java:1680) org.jruby.RubyKernel.send19(org/jruby/RubyKernel.java:1998) org.jruby.RubyKernel$INVOKER$s$send19.call(org/jruby/RubyKernel$INVOKER$s$send19.gen) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther1:send(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in DB(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/reports_runner.rb:36) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Done. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Christine Di Bella Sent: Wednesday, April 26, 2017 11:55:48 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Daniel, I?m not familiar with that being a reason for having problems with reports, but others may be able to help with that. What I can point you to is the information about enabling reports for versions through 1.5.4 in the user manual at https://docs.archivesspace.org/Default.htm#ReportsEnabling.htm. Jasper reports has been removed from the application starting with 2.0.0, so these steps will no longer be necessary in future upgrades. Reports are an area of the application that is under active development at this time and we hope to have more updates available soon. An alternate that some people are using with success is setting up an ODBC connection or otherwise hooking ArchivesSpace up to output data to an external program. As one example, Nancy Enneking of the Getty presented a lightning talk titled DIY Reports in ArchivesSpace at a session called Making ArchivesSpace Work for You at SAA last summer. Nancy?s talk is in the file posted at http://schd.ws/hosted_files/archives2016/3e/Session501-All_presenters.pptx; Nancy?s starts on page 40. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Wednesday, April 26, 2017 11:37 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Christine, We are running v1.5.4. I also got some advice to do: "Make sure you have AS created User Defined functions (about 63 functions) present in the underlying MYSQL by running "show function status" under MySQL prompt." So right now, I am heading over to our IT guys and see if they can "show function status" under MYSQL. Would you agree with this assessment? Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Wednesday, April 26, 2017 10:18:09 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Dear Daniel, What version of ArchivesSpace are you running? There are some differences between different versions for what you need to do to run reports, and also which reports run successfully. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Tuesday, April 25, 2017 3:17 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports I keep on getting a failed status on any kind of report I run. I've tried generating all the different types of reports you can export and our different repositories. One repository are records we hand typed in the other is a repository we successful migrated into. This particular report was for accessions record reports. Here is the log: Thank you. Generating report Error executing SQL statement for : accessionsRecord net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) java.lang.Thread.run(java/lang/Thread.java:745) Done. Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Thu Apr 27 12:14:46 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 27 Apr 2017 16:14:46 +0000 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports In-Reply-To: References: , , Message-ID: Hi Daniel, You still need to have a MySQL backend, not the embedded database, to run reports. This message looks like maybe your test machine isn't using MySQL. Which platform are you on? The basic instructions are available at http://archivesspace.github.io/archivesspace/user/running-archivesspace-against-mysql/ that should get you through a Linux installation and some people in the community have also prepared some really great instructions for Windows, if you need them. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Thursday, April 27, 2017 12:08 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports We set up a test machine with V2.0 and followed the Manuel, the software works but still having problems with the reports. This was the failed status log: Follow Log Generating report Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: FUNCTION archivesspace.GetAccessionProcessed does not exist java.lang.reflect.Constructor.newInstance(java/lang/reflect/Constructor.java:423) com.mysql.jdbc.Util.handleNewInstance(com/mysql/jdbc/Util.java:425) com.mysql.jdbc.Util.getInstance(com/mysql/jdbc/Util.java:408) com.mysql.jdbc.SQLError.createSQLException(com/mysql/jdbc/SQLError.java:943) com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3973) com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3909) com.mysql.jdbc.MysqlIO.sendCommand(com/mysql/jdbc/MysqlIO.java:2527) com.mysql.jdbc.MysqlIO.sqlQueryDirect(com/mysql/jdbc/MysqlIO.java:2680) com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2497) com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2455) com.mysql.jdbc.StatementImpl.executeQuery(com/mysql/jdbc/StatementImpl.java:1369) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther1:executeQuery(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.logging.log_yield(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/logging.rb:33) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther8:log_yield(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.statement(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:646) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther25:statement(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther2:hold(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther35:synchronize(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther7:execute(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther2:execute(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.fetch_rows(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther7:fetch_rows(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:139) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.each(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:139) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther11:each(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:71) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.columns(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:71) RUBY.headers(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/abstract_report.rb:40) RUBY.each(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/csv_response.rb:10) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/csv_response.rb:20) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:27) RUBY.block in run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/reports_runner.rb:37) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in transaction(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions._transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.invokeOther14:_transaction(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.block in transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther2:hold(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.invokeOther35:synchronize(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther2:transaction(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.transaction(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther6:transaction(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:305) org.jruby.RubyFixnum$INVOKER$i$0$0$times.call(org/jruby/RubyFixnum$INVOKER$i$0$0$times.gen) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther50:times(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) org.jruby.RubyClass.finvoke(org/jruby/RubyClass.java:522) org.jruby.RubyBasicObject.send19(org/jruby/RubyBasicObject.java:1680) org.jruby.RubyKernel.send19(org/jruby/RubyKernel.java:1998) org.jruby.RubyKernel$INVOKER$s$send19.call(org/jruby/RubyKernel$INVOKER$s$send19.gen) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther1:send(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in DB(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/reports_runner.rb:36) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Done. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Wednesday, April 26, 2017 11:55:48 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Daniel, I'm not familiar with that being a reason for having problems with reports, but others may be able to help with that. What I can point you to is the information about enabling reports for versions through 1.5.4 in the user manual at https://docs.archivesspace.org/Default.htm#ReportsEnabling.htm. Jasper reports has been removed from the application starting with 2.0.0, so these steps will no longer be necessary in future upgrades. Reports are an area of the application that is under active development at this time and we hope to have more updates available soon. An alternate that some people are using with success is setting up an ODBC connection or otherwise hooking ArchivesSpace up to output data to an external program. As one example, Nancy Enneking of the Getty presented a lightning talk titled DIY Reports in ArchivesSpace at a session called Making ArchivesSpace Work for You at SAA last summer. Nancy's talk is in the file posted at http://schd.ws/hosted_files/archives2016/3e/Session501-All_presenters.pptx; Nancy's starts on page 40. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Wednesday, April 26, 2017 11:37 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Christine, We are running v1.5.4. I also got some advice to do: "Make sure you have AS created User Defined functions (about 63 functions) present in the underlying MYSQL by running "show function status" under MySQL prompt." So right now, I am heading over to our IT guys and see if they can "show function status" under MYSQL. Would you agree with this assessment? Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Wednesday, April 26, 2017 10:18:09 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Dear Daniel, What version of ArchivesSpace are you running? There are some differences between different versions for what you need to do to run reports, and also which reports run successfully. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Tuesday, April 25, 2017 3:17 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports I keep on getting a failed status on any kind of report I run. I've tried generating all the different types of reports you can export and our different repositories. One repository are records we hand typed in the other is a repository we successful migrated into. This particular report was for accessions record reports. Here is the log: Thank you. Generating report Error executing SQL statement for : accessionsRecord net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) java.lang.Thread.run(java/lang/Thread.java:745) Done. Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: From Daniel.Thacker at tamuk.edu Thu Apr 27 12:19:10 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Thu, 27 Apr 2017 16:19:10 +0000 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports In-Reply-To: References: , , , Message-ID: Hello Christine, Thank you for your response. I am standing right next to our tech guy and he says we are using MySQL and UBUNTU 16 server. We checked the basic instructions and those are the ones he used. Thanks again, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Christine Di Bella Sent: Thursday, April 27, 2017 11:14:46 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Daniel, You still need to have a MySQL backend, not the embedded database, to run reports. This message looks like maybe your test machine isn?t using MySQL. Which platform are you on? The basic instructions are available at http://archivesspace.github.io/archivesspace/user/running-archivesspace-against-mysql/ that should get you through a Linux installation and some people in the community have also prepared some really great instructions for Windows, if you need them. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Thursday, April 27, 2017 12:08 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports We set up a test machine with V2.0 and followed the Manuel, the software works but still having problems with the reports. This was the failed status log: Follow Log Generating report Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: FUNCTION archivesspace.GetAccessionProcessed does not exist java.lang.reflect.Constructor.newInstance(java/lang/reflect/Constructor.java:423) com.mysql.jdbc.Util.handleNewInstance(com/mysql/jdbc/Util.java:425) com.mysql.jdbc.Util.getInstance(com/mysql/jdbc/Util.java:408) com.mysql.jdbc.SQLError.createSQLException(com/mysql/jdbc/SQLError.java:943) com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3973) com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3909) com.mysql.jdbc.MysqlIO.sendCommand(com/mysql/jdbc/MysqlIO.java:2527) com.mysql.jdbc.MysqlIO.sqlQueryDirect(com/mysql/jdbc/MysqlIO.java:2680) com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2497) com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2455) com.mysql.jdbc.StatementImpl.executeQuery(com/mysql/jdbc/StatementImpl.java:1369) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther1:executeQuery(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.logging.log_yield(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/logging.rb:33) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther8:log_yield(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.statement(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:646) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther25:statement(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther2:hold(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther35:synchronize(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther7:execute(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther2:execute(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.fetch_rows(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther7:fetch_rows(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:139) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.each(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:139) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther11:each(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:71) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.columns(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:71) RUBY.headers(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/abstract_report.rb:40) RUBY.each(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/csv_response.rb:10) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/csv_response.rb:20) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:27) RUBY.block in run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/reports_runner.rb:37) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in transaction(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions._transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.invokeOther14:_transaction(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.block in transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther2:hold(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.invokeOther35:synchronize(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther2:transaction(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.transaction(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther6:transaction(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:305) org.jruby.RubyFixnum$INVOKER$i$0$0$times.call(org/jruby/RubyFixnum$INVOKER$i$0$0$times.gen) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther50:times(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) org.jruby.RubyClass.finvoke(org/jruby/RubyClass.java:522) org.jruby.RubyBasicObject.send19(org/jruby/RubyBasicObject.java:1680) org.jruby.RubyKernel.send19(org/jruby/RubyKernel.java:1998) org.jruby.RubyKernel$INVOKER$s$send19.call(org/jruby/RubyKernel$INVOKER$s$send19.gen) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther1:send(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in DB(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/reports_runner.rb:36) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Done. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Wednesday, April 26, 2017 11:55:48 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Daniel, I?m not familiar with that being a reason for having problems with reports, but others may be able to help with that. What I can point you to is the information about enabling reports for versions through 1.5.4 in the user manual at https://docs.archivesspace.org/Default.htm#ReportsEnabling.htm. Jasper reports has been removed from the application starting with 2.0.0, so these steps will no longer be necessary in future upgrades. Reports are an area of the application that is under active development at this time and we hope to have more updates available soon. An alternate that some people are using with success is setting up an ODBC connection or otherwise hooking ArchivesSpace up to output data to an external program. As one example, Nancy Enneking of the Getty presented a lightning talk titled DIY Reports in ArchivesSpace at a session called Making ArchivesSpace Work for You at SAA last summer. Nancy?s talk is in the file posted at http://schd.ws/hosted_files/archives2016/3e/Session501-All_presenters.pptx; Nancy?s starts on page 40. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Wednesday, April 26, 2017 11:37 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Christine, We are running v1.5.4. I also got some advice to do: "Make sure you have AS created User Defined functions (about 63 functions) present in the underlying MYSQL by running "show function status" under MySQL prompt." So right now, I am heading over to our IT guys and see if they can "show function status" under MYSQL. Would you agree with this assessment? Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Wednesday, April 26, 2017 10:18:09 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Dear Daniel, What version of ArchivesSpace are you running? There are some differences between different versions for what you need to do to run reports, and also which reports run successfully. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Tuesday, April 25, 2017 3:17 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports I keep on getting a failed status on any kind of report I run. I've tried generating all the different types of reports you can export and our different repositories. One repository are records we hand typed in the other is a repository we successful migrated into. This particular report was for accessions record reports. Here is the log: Thank you. Generating report Error executing SQL statement for : accessionsRecord net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) java.lang.Thread.run(java/lang/Thread.java:745) Done. Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Thu Apr 27 12:31:31 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 27 Apr 2017 16:31:31 +0000 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports In-Reply-To: References: , , , Message-ID: Hi Daniel, I'll put this over into a tech support ticket then, and you'll see another message from me about that in a minute. When it gets resolved, it'd be great if you'd post the answer back to the listserv. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Thursday, April 27, 2017 12:19 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hello Christine, Thank you for your response. I am standing right next to our tech guy and he says we are using MySQL and UBUNTU 16 server. We checked the basic instructions and those are the ones he used. Thanks again, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Thursday, April 27, 2017 11:14:46 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Daniel, You still need to have a MySQL backend, not the embedded database, to run reports. This message looks like maybe your test machine isn't using MySQL. Which platform are you on? The basic instructions are available at http://archivesspace.github.io/archivesspace/user/running-archivesspace-against-mysql/ that should get you through a Linux installation and some people in the community have also prepared some really great instructions for Windows, if you need them. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Thursday, April 27, 2017 12:08 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports We set up a test machine with V2.0 and followed the Manuel, the software works but still having problems with the reports. This was the failed status log: Follow Log Generating report Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: FUNCTION archivesspace.GetAccessionProcessed does not exist java.lang.reflect.Constructor.newInstance(java/lang/reflect/Constructor.java:423) com.mysql.jdbc.Util.handleNewInstance(com/mysql/jdbc/Util.java:425) com.mysql.jdbc.Util.getInstance(com/mysql/jdbc/Util.java:408) com.mysql.jdbc.SQLError.createSQLException(com/mysql/jdbc/SQLError.java:943) com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3973) com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3909) com.mysql.jdbc.MysqlIO.sendCommand(com/mysql/jdbc/MysqlIO.java:2527) com.mysql.jdbc.MysqlIO.sqlQueryDirect(com/mysql/jdbc/MysqlIO.java:2680) com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2497) com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2455) com.mysql.jdbc.StatementImpl.executeQuery(com/mysql/jdbc/StatementImpl.java:1369) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther1:executeQuery(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.logging.log_yield(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/logging.rb:33) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther8:log_yield(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.statement(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:646) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther25:statement(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther2:hold(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther35:synchronize(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther7:execute(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther2:execute(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.fetch_rows(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther7:fetch_rows(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:139) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.each(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:139) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther11:each(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:71) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.columns(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:71) RUBY.headers(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/abstract_report.rb:40) RUBY.each(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/csv_response.rb:10) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/csv_response.rb:20) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:27) RUBY.block in run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/reports_runner.rb:37) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in transaction(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions._transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.invokeOther14:_transaction(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.block in transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther2:hold(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.invokeOther35:synchronize(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther2:transaction(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.transaction(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther6:transaction(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:305) org.jruby.RubyFixnum$INVOKER$i$0$0$times.call(org/jruby/RubyFixnum$INVOKER$i$0$0$times.gen) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther50:times(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) org.jruby.RubyClass.finvoke(org/jruby/RubyClass.java:522) org.jruby.RubyBasicObject.send19(org/jruby/RubyBasicObject.java:1680) org.jruby.RubyKernel.send19(org/jruby/RubyKernel.java:1998) org.jruby.RubyKernel$INVOKER$s$send19.call(org/jruby/RubyKernel$INVOKER$s$send19.gen) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther1:send(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in DB(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/reports_runner.rb:36) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Done. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Wednesday, April 26, 2017 11:55:48 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Daniel, I'm not familiar with that being a reason for having problems with reports, but others may be able to help with that. What I can point you to is the information about enabling reports for versions through 1.5.4 in the user manual at https://docs.archivesspace.org/Default.htm#ReportsEnabling.htm. Jasper reports has been removed from the application starting with 2.0.0, so these steps will no longer be necessary in future upgrades. Reports are an area of the application that is under active development at this time and we hope to have more updates available soon. An alternate that some people are using with success is setting up an ODBC connection or otherwise hooking ArchivesSpace up to output data to an external program. As one example, Nancy Enneking of the Getty presented a lightning talk titled DIY Reports in ArchivesSpace at a session called Making ArchivesSpace Work for You at SAA last summer. Nancy's talk is in the file posted at http://schd.ws/hosted_files/archives2016/3e/Session501-All_presenters.pptx; Nancy's starts on page 40. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Wednesday, April 26, 2017 11:37 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Christine, We are running v1.5.4. I also got some advice to do: "Make sure you have AS created User Defined functions (about 63 functions) present in the underlying MYSQL by running "show function status" under MySQL prompt." So right now, I am heading over to our IT guys and see if they can "show function status" under MYSQL. Would you agree with this assessment? Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Wednesday, April 26, 2017 10:18:09 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Dear Daniel, What version of ArchivesSpace are you running? There are some differences between different versions for what you need to do to run reports, and also which reports run successfully. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Tuesday, April 25, 2017 3:17 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports I keep on getting a failed status on any kind of report I run. I've tried generating all the different types of reports you can export and our different repositories. One repository are records we hand typed in the other is a repository we successful migrated into. This particular report was for accessions record reports. Here is the log: Thank you. Generating report Error executing SQL statement for : accessionsRecord net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) java.lang.Thread.run(java/lang/Thread.java:745) Done. Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: From Daniel.Thacker at tamuk.edu Thu Apr 27 12:34:46 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Thu, 27 Apr 2017 16:34:46 +0000 Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports In-Reply-To: References: , , , , Message-ID: Of course! Thank you! Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Christine Di Bella Sent: Thursday, April 27, 2017 11:31:31 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Daniel, I?ll put this over into a tech support ticket then, and you?ll see another message from me about that in a minute. When it gets resolved, it?d be great if you?d post the answer back to the listserv. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Thursday, April 27, 2017 12:19 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hello Christine, Thank you for your response. I am standing right next to our tech guy and he says we are using MySQL and UBUNTU 16 server. We checked the basic instructions and those are the ones he used. Thanks again, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Thursday, April 27, 2017 11:14:46 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Daniel, You still need to have a MySQL backend, not the embedded database, to run reports. This message looks like maybe your test machine isn?t using MySQL. Which platform are you on? The basic instructions are available at http://archivesspace.github.io/archivesspace/user/running-archivesspace-against-mysql/ that should get you through a Linux installation and some people in the community have also prepared some really great instructions for Windows, if you need them. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Thursday, April 27, 2017 12:08 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports We set up a test machine with V2.0 and followed the Manuel, the software works but still having problems with the reports. This was the failed status log: Follow Log Generating report Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: FUNCTION archivesspace.GetAccessionProcessed does not exist java.lang.reflect.Constructor.newInstance(java/lang/reflect/Constructor.java:423) com.mysql.jdbc.Util.handleNewInstance(com/mysql/jdbc/Util.java:425) com.mysql.jdbc.Util.getInstance(com/mysql/jdbc/Util.java:408) com.mysql.jdbc.SQLError.createSQLException(com/mysql/jdbc/SQLError.java:943) com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3973) com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3909) com.mysql.jdbc.MysqlIO.sendCommand(com/mysql/jdbc/MysqlIO.java:2527) com.mysql.jdbc.MysqlIO.sqlQueryDirect(com/mysql/jdbc/MysqlIO.java:2680) com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2497) com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2455) com.mysql.jdbc.StatementImpl.executeQuery(com/mysql/jdbc/StatementImpl.java:1369) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:453) org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:314) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther1:executeQuery(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.logging.log_yield(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/logging.rb:33) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther8:log_yield(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:250) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.statement(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:646) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther25:statement(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.block in execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:245) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:85) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther2:hold(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther35:synchronize(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther7:execute(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.execute(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:911) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.invokeOther2:execute(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/adapters//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.adapters.jdbc.fetch_rows(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:725) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther7:fetch_rows(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:139) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.each(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:139) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.invokeOther11:each(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/dataset//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:71) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.dataset.actions.columns(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/dataset/actions.rb:71) RUBY.headers(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/abstract_report.rb:40) RUBY.each(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/csv_response.rb:10) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/csv_response.rb:20) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:27) RUBY.block in run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/reports_runner.rb:37) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:111) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in transaction(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:75) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions._transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.invokeOther14:_transaction(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.block in transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.connection_pool.threaded.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.invokeOther2:hold(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.connecting.synchronize(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.invokeOther35:synchronize(home/administrator/archivesspace/gems/gems/sequel_minus_4_dot_20_dot_0/lib/sequel/database//home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) home.administrator.archivesspace.gems.gems.sequel_minus_4_dot_20_dot_0.lib.sequel.database.transactions.transaction(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther2:transaction(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.transaction(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:74) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther6:transaction(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:110) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:305) org.jruby.RubyFixnum$INVOKER$i$0$0$times.call(org/jruby/RubyFixnum$INVOKER$i$0$0$times.gen) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther50:times(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:107) org.jruby.RubyClass.finvoke(org/jruby/RubyClass.java:522) org.jruby.RubyBasicObject.send19(org/jruby/RubyBasicObject.java:1680) org.jruby.RubyKernel.send19(org/jruby/RubyKernel.java:1998) org.jruby.RubyKernel$INVOKER$s$send19.call(org/jruby/RubyKernel$INVOKER$s$send19.gen) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.invokeOther1:send(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/model//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.model.db.block in DB(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:432) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/reports_runner.rb:36) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther43:run(home/administrator/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) home.administrator.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126) RUBY.block in start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169) org.jruby.RubyProc.call(org/jruby/RubyProc.java:289) org.jruby.RubyProc.call(org/jruby/RubyProc.java:246) java.lang.Thread.run(java/lang/Thread.java:748) Done. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Wednesday, April 26, 2017 11:55:48 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Daniel, I?m not familiar with that being a reason for having problems with reports, but others may be able to help with that. What I can point you to is the information about enabling reports for versions through 1.5.4 in the user manual at https://docs.archivesspace.org/Default.htm#ReportsEnabling.htm. Jasper reports has been removed from the application starting with 2.0.0, so these steps will no longer be necessary in future upgrades. Reports are an area of the application that is under active development at this time and we hope to have more updates available soon. An alternate that some people are using with success is setting up an ODBC connection or otherwise hooking ArchivesSpace up to output data to an external program. As one example, Nancy Enneking of the Getty presented a lightning talk titled DIY Reports in ArchivesSpace at a session called Making ArchivesSpace Work for You at SAA last summer. Nancy?s talk is in the file posted at http://schd.ws/hosted_files/archives2016/3e/Session501-All_presenters.pptx; Nancy?s starts on page 40. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Wednesday, April 26, 2017 11:37 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Hi Christine, We are running v1.5.4. I also got some advice to do: "Make sure you have AS created User Defined functions (about 63 functions) present in the underlying MYSQL by running "show function status" under MySQL prompt." So right now, I am heading over to our IT guys and see if they can "show function status" under MYSQL. Would you agree with this assessment? Thank you, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Christine Di Bella > Sent: Wednesday, April 26, 2017 10:18:09 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Keep getting Failed status on generating reports Dear Daniel, What version of ArchivesSpace are you running? There are some differences between different versions for what you need to do to run reports, and also which reports run successfully. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Daniel L Thacker Sent: Tuesday, April 25, 2017 3:17 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Keep getting Failed status on generating reports I keep on getting a failed status on any kind of report I run. I've tried generating all the different types of reports you can export and our different repositories. One repository are records we hand typed in the other is a repository we successful migrated into. This particular report was for accessions record reports. Here is the log: Thank you. Generating report Error executing SQL statement for : accessionsRecord net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(net/sf/jasperreports/engine/query/JRJdbcQueryExecuter.java:240) net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:1114) net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(net/sf/jasperreports/engine/fill/JRFillDataset.java:691) net.sf.jasperreports.engine.fill.JRBaseFiller.setParameters(net/sf/jasperreports/engine/fill/JRBaseFiller.java:1314) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:931) net.sf.jasperreports.engine.fill.JRBaseFiller.fill(net/sf/jasperreports/engine/fill/JRBaseFiller.java:873) net.sf.jasperreports.engine.fill.JRFiller.fill(net/sf/jasperreports/engine/fill/JRFiller.java:87) net.sf.jasperreports.engine.JasperFillManager.fill(net/sf/jasperreports/engine/JasperFillManager.java:287) net.sf.jasperreports.engine.JasperFillManager.fillReport(net/sf/jasperreports/engine/JasperFillManager.java:760) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:22) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) Sequel::ThreadedConnectionPool.hold(/home/administrator/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:21) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:143) org.jruby.RubyFixnum.times(org/jruby/RubyFixnum.java:280) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:131) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) DB.open(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:127) RUBY.fill(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:20) RUBY.render(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/reports/jdbc_report.rb:75) RUBY.generate(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports/report_response.rb:25) RUBY.run(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/reports_runner.rb:43) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) BackgroundJobQueue.run_pending_job(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:113) RUBY.start_background_thread(/home/administrator/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:153) java.lang.Thread.run(java/lang/Thread.java:745) Done. Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4144 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Thu Apr 27 15:24:45 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 27 Apr 2017 19:24:45 +0000 Subject: [Archivesspace_Users_Group] new suggested mappings for ArchivesSpace MODS and DC digital object exports available for comment Message-ID: Hello ArchivesSpace members, Thanks to the hard work of the Digital Objects Exports working group, new suggested mappings for two of the exports currently offered by the ArchivesSpace digital objects module (Dublin Core, MODS) have been drafted and are ready to be shared for wider comment. A suggested mapping for the METS export will be available soon. . You can access the mappings by visiting the working group's web page or the links in comments on the relevant JIRA issues. Of note for those interested in the METS mapping: while ArchivesSpace currently provides for MODS descriptive metadata only within METS records, with the change in mapping we would also aim to provide the option to select either Dublin Core or MODS in the export in the application. Either of these options would reflect the mapping of the standalone export. So please do look at the Dublin Core and MODS mappings in that light as well. Dublin Core: https://archivesspace.atlassian.net/browse/AR-921 MODS: https://archivesspace.atlassian.net/browse/AR-920 METS: https://archivesspace.atlassian.net/browse/AR-919, https://archivesspace.atlassian.net/browse/AR-788, and https://archivesspace.atlassian.net/browse/AR-781 You may comment on any or all of the mappings. Please consider them both in terms of your current (or anticipated workflow) and your preferred workflow for the future and let us know if there is anything missing or anything that would negatively impact what you need to do. (And, of course, we're also very happy to hear confirmation if the proposed mappings suit your purposes as is.) Please submit your feedback by commenting in the mapping files, commenting on the JIRA issues or emailing me directly. As much as possible, we'd like to receive feedback by May 19. Once the mappings have been finalized, we can schedule the revisions, as well as the additional choice for descriptive metadata included with the METS export, for inclusion in the application. Thanks in advance for your feedback and participation in this process. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 4144 bytes Desc: image003.jpg URL: From blake.graham at unl.edu Thu Apr 27 18:41:44 2017 From: blake.graham at unl.edu (Blake Graham) Date: Thu, 27 Apr 2017 22:41:44 +0000 Subject: [Archivesspace_Users_Group] just another upgrade question Message-ID: Hi all, We're attempting to upgrade from 1.4.2 to 1.5 on a development server, but we keep encountering some issues for extent subrecords. After the upgrade attempt(s), we're seeing lots of unnecessary extent subrecords, which are showing "0.00 unknown." It seems like an empty subrecord is being created for each subrecord found in v.1.4.2. Here's a snippet of extent data when downloaded as ead: 0.00 unknown 0.00 unknown 0.00 unknown 0.00 unknown 58.00 microfilm reel(s) 29.00 microfilm reel(s) 11.00 microfilm reel(s) 15.00 microfilm reel(s) Note - issue is present with or without the barcoder plugin used. Any ideas for why this is happening? Thanks in advance. Cheers, Blake Blake Graham Digital Archivist | Assistant Professor University of Nebraska-Lincoln Archives & Special Collections (402) 472-3817 | blake.graham at unl.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Grant.Buttars at ed.ac.uk Fri Apr 28 03:45:56 2017 From: Grant.Buttars at ed.ac.uk (BUTTARS Grant) Date: Fri, 28 Apr 2017 07:45:56 +0000 Subject: [Archivesspace_Users_Group] Digital Object csv import: multiple file versions In-Reply-To: <905C1D46-E7B5-4BFA-949A-918889EA3EAC@eservices.virginia.edu> References: <905C1D46-E7B5-4BFA-949A-918889EA3EAC@eservices.virginia.edu> Message-ID: Hi Steve, Thanks for this. I had experimented with using EAD before but discounted it. However, my overall thinking has developed somewhat since then so it might be worth revisiting this again. I?m going to send this to colleagues who understand the API better than I do. If it?s ok with you, they may want to discuss in more detail. Best wishes Grant --------------------------------- Grant E. L. Buttars, | Deputy University Archivist | Special Collections | Centre for Research Collections | Division of Library and University Collections | University of Edinburgh George Square, Edinburgh | EH8 9LJ | http://www.ed.ac.uk/is/crc | tel: 0131 650 8379 | direct dial: 0131 651 3852 ================================= Coming to consult something? Please see http://www.ed.ac.uk/is/crc for service information Follow CRC [FaceBook-icon2][Twitter-icon2] Facebook: https://www.facebook.com/crc.edinburgh Twitter: https://twitter.com/CRC_EdUni Follow Archives [Twitter-icon2][Flickr-icon2][wordpress] Twitter: https://twitter.com/euarchives Flickr: http://www.flickr.com/photos/edinburgh-university-archives Blog: http://libraryblogs.is.ed.ac.uk/edinburghuniversityarchives Follow me professionally [Twitter-icon2][linkedin] Twitter: https://twitter.com/ButtarsGrant LinkedIn: https://www.linkedin.com/pub/grant-buttars/61/7b3/a09 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: 24 April 2017 17:11 To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Digital Object csv import: multiple file versions I don?t believe you can do it with the CSV import. EAD import will treat multiple within as multiple file versions to one digital object. ( If you already have the resource those digital objects should be bound to in ArchivesSpace, there may be some cases where the easiest(*) thing to do is to export the object to EAD, add the digital objects to the appropriate components with a XSLT stylesheet, delete resource and reimport modified EAD in ArchivesSpace. ) The other alternative is to script something using the backend API. ( We?re testing using the API to connect our digitization tracking system to ArchiveSpace: tracking system keeps a link to ASpace archival_object, attaches an external_id in ASpace pointing back to tracking system item, and creates a digital_object attached to archival_object with URI to IIIF manifest. ) [ (*) ?easiest? only if XSLT transforms of EAD is what you are already used to doing. ] ? Steve M. On Apr 24, 2017, at 7:36 AM, BUTTARS Grant > wrote: I?m currently working on importing digital object metadata and want to include more than one file version per object. The template only allows for one. Ideally, I?d also like to include external document links and notes (again none of these are in the template). Is there any way of achieving any of these? Many thanks Grant -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 4228 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image010.jpg Type: image/jpeg Size: 1176 bytes Desc: image010.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image011.jpg Type: image/jpeg Size: 1147 bytes Desc: image011.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image012.jpg Type: image/jpeg Size: 1287 bytes Desc: image012.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image013.png Type: image/png Size: 2587 bytes Desc: image013.png URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: not available URL: From Daniel.Thacker at tamuk.edu Fri Apr 28 18:18:06 2017 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Fri, 28 Apr 2017 22:18:06 +0000 Subject: [Archivesspace_Users_Group] Our Solution to Running Reports Message-ID: We were asked to post our solution once we talked to the LYRASIS Support Desk and resolved our issue. Here it is: Our problem was that we couldn't run reports on V1.5.4 and V2.0.0. The problem, as explained to me by our tech guy, was that when we backed up ArchivesSpace V1.52 to go to V1.5.4 we did a short back-up instead of a long back-up. The short back-up got all of our data but not the functions from the DB. We put those functions back and we are now able to run reports. Here is the part of the conversation to hopefully make it more clear if it isn't already: LYRASIS Support Desk: Hi Daniel, There is something up with the stored functions on your database. Seeing this: Java::ComMysqlJdbcExceptionsJdbc4::MySQLSyntaxErrorException: FUNCTION archivesspace.GetAccessionProcessed does not exist Makes me think your missing at least that one function. You can see it in the code here: https://github.com/archivesspace/archivesspace/blob/5e1ca66f1f04f142f2695024efb7200825046325/common/db/migrations/055_add_reports_stored_functions.rb#L261 Was your database maybe restored from a backup? You'll need to get those functions restored. US- TAMUK Yes, they were restored from the backup. How do we restore the functions? LYRASIS Support Desk: Aha, thank makes sense. If you have the original DB you can pull out the functions, something like: mysqldump --routines --no-create-info --no-data --no-create-db --skip-opt archivesspace > as-functions.sql Then you can put those back into your real database: mysql archivesspace < as-functions.sql Be sure to back things up before doing that, just in case. I can pull the functions out from a DB here if you don't have one there you can use, just let me know. END Hope this helps and thank you to everyone who helped and inquired! Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: