It's probably a problem brought on by the change of time this week.
Try this:
MySQL [archivesspace]> select * from auth_db;
+--+--+-+-+--+
| id | username |
Oh, I missed the second part:
So, that endpoint returns the XML directly as the body of the response in
memory. The JSONDecodeError you’re getting is due to trying to decode this
body as JSON, when what you actually have is XML!
If you want to save it to the filesystem, you just need to write
I would also add that if you want the EAD, it may be simpler to access it from
the OAI endpoint, but only if OAI is configured properly. Try downloading a
resource using oai_ead metadata from the oai/sample page, to see if it’s
configured properly and what the resource URLs will look like.
—
Hi Corey,
Splitting this into two sections – the first is a description of what’s
happening and should immediately fix your current issue, the second is some
advice going forward re: using ASnake.
You appear to have found a bug in the ASpace API! From what I can tell, all_ids
is not actually
If you import a collection from an EAD file then any persname, famname and
corpname it contains will be converted into agent records (the ones not already
in the system with precisely the same spelling and source - any small
differences will created duplicates) and linked to the resource and/or
