archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of
> mang@rice.edu
> *Sent:* Monday, October 24, 2022 4:19 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] User-define
of
> mang@rice.edu
> *Sent:* Monday, October 24, 2022 4:19 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML
>
> We see the following error in the expor
rasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML
>
> We see the following error in the exported marcxml file with the plugin
> enabled. Our AS version is 2.7.1.
>
> {"error":"wrong number of arguments (2 for 1)"}
>
>
>
We see the following error in the exported marcxml file with the plugin
enabled. Our AS version is 2.7.1.
{"error":"wrong number of arguments (2 for 1)"}
Mang Sun
Rice U.
On Wed, Oct 19, 2022 at 4:33 PM Joshua D. Shaw
wrote:
> Hi Rebecca
>
> This should get you
Sorry, please ignore my reply which was mistakenly sent~
Mang
On Mon, Jul 25, 2022 at 1:04 PM wrote:
> I see under the Subject Source there is already a local entry. So changing
> TARO to local will cause conflict in subject values. Can you
> suggest another value for TARO's value?
>
> Mang
>
I see under the Subject Source there is already a local entry. So changing
TARO to local will cause conflict in subject values. Can you
suggest another value for TARO's value?
Mang
On Tue, Jan 26, 2016 at 12:47 PM Noah Huffman wrote:
> Hi Kate,
>
>
>
> I think you’ve got the right file. From
asis.org
on behalf of
Mang Sun
*Sent:* Thursday, April 16, 2020 12:53 PM
*To:* archivesspace_users_group@lyralists.lyrasis.org
*Subject:* [Archivesspace_Users_Group] Can't get ArchivesSpace
(ASpace) connected to my SQL5.52 and 5.6
We are trying to move our ASpace to a new virtual box where
EAD UNCOMMITTED."
*From:* archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of
Mang Sun
*Sent:* Thursday, April 16, 2020 12:53 PM
*To:* archivesspace_users_group@lyralists.lyrasis.org
*Subject:* [Archivesspace_Users_Group] Can't get Ar
The version of our ASpace is v2.2.1.
Mang
On 4/16/2020 11:53 AM, Mang Sun wrote:
We are trying to move our ASpace to a new virtual box where only MySQL
v5.5.52 and 5.6 are available from our current physical box where
MySQL v.5.1.37 is running. However we keep seeing the following errors
We are trying to move our ASpace to a new virtual box where only MySQL
v5.5.52 and 5.6 are available from our current physical box where MySQL
v.5.1.37 is running. However we keep seeing the following errors
(excerpted) related to login authentication with both versions. MySQL
user name/passwd
ot;
cause premature end of harvesting? We have more than 1000 records at
collection level.
Thank you.
Mang Sun
Rice U.
On 10/22/2018 7:51 AM, Christine Di Bella wrote:
Thanks for this, Terry. We track development requests in JIRA:
http://development.archivesspace.org. I’d encourage you
I guess jump straight from 1.5.x to 2.2.1 may possibly miss the
migration (convert to UTF-8) step for that table but upgrade first to
2.1.2 can get the said migration step applied.
Mang
On 11/28/2017 12:37 PM, Jeff Earickson wrote:
All,
Problem Solved!!!
The issue was thus, near the top
Our running v2.2.1 test instance uses the v5.1.34 one.
Mang
Rice U.
On 11/28/2017 11:13 AM, Adam Jazairi wrote:
Hi Jeff,
Could you try switching back to mysql-connector-java-5.1.40 or
mysql-connector-java-5.1.39 and see if that fixes it? We've had
problems in the past with versions above
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
Steve,
You are not alone. We also ran into indexing error when trying to test
upgrade v1.5.1 to v.1.5.2 and see no record found again after the test
upgrade.
LYRASIS Support Desk ever helped us in solving a similar indexing
problem (no record found ) which ever drove me mad :) when upgrading
Any ArchivesSpace tech guys/developers going to Code4Lib2017?
Mang Sun
Rice U.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
540-464-7572
*From:*archivesspace_users_group-boun...@lyralists.lyrasis.org
<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] *On
Behalf Of *Mang Sun
*Sent:* Wednesday, September 14, 2016 3:00 PM
*To:* Archivesspace Users Group
is.org
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] *On
Behalf Of *Mang Sun
*Sent:* Friday, September 9, 2016 12:31 PM
*To:* Archivesspace Users Group
<archivesspace_users_group@lyralists.lyrasis.org>
*Subject:* Re: [Archivesspace_Users_Group] No record found after test
migration
Sally,
by the way, we see the same issue with 1.5.0 and 1.5.1.
-Mang
On 9/9/2016 8:52 AM, Sally Vermaaten wrote:
Hi Mang Sun,
I agree with Joshua - this sounds to me like an indexing problem to
me. In the course of upgrading to 1.5.0 did you delete the
data/solr_index/index directory
19 matches
Mail list logo
