Date
...
Time | Item | Notes | Action items |
---|---|---|---|
5-10 min | Review action items | ||
5 min | Working group timeline | ||
15-20 min | Program details (below) | ||
Program: Lightning Round |
| ||
Program: Discussions |
| ||
Program: Speakers |
| ||
Afternoon program |
A better understanding of what data wouldn't transfer and why and how to troubleshoot that. Ruby on Rails. I was somewhat new to it at the time, but the more I learned about RoR, the more AS made sense to me. How to robustly use the API If I had known how much extra time, work, money, and technology it would take to use the digital objects module we probably would have stayed with Archon. Getting our material online quickly and in a way our users can find it with one click was really the goal, and I still haven't found a way to do that with this system. I do feel we have to move forward with this if we want to keep up with the profession, but the system capabilities are so far beyond our needs that they make it difficult to implement, or know if we are implementing it properly. For instance, we don't have external reporting software or a digital asset management system, or onsite tech people who would make it easy to customize PUI. Basically if it can't be customized from the user accounts, we have to pay someone to do it. SO, the point of that is to say that I would really value a quick and dirty "Implementing ASpace on a Dime with a Staff of One for a Small Collection" kind of class. Top Container information, Agent/Subject Authority Files, Rights Statments, Working with the API This is not an answer to this question, but I don't see a general comments box. We are a new archives, so we did not have to import any data into Aspace. You did not offer that as an option in one of your first questions, which is understandable, but I wanted to make that clear. I wish I had known that I would need substantially more knowledge of APIs and Python in order to make ArchivesSpace work like I need it to. I don't know of a way to acquire that knowledge other than using my employee tuition discount to take computer science classes, which I will be doing this fall. The whole plugins / customization deal is still mysterious to me! I know next to nothing about ruby, yml, APIs, or git(hub), and it limits what we can do here compared to what I see other repositories doing. Put in the labor at the front end. The more information you put into AS the more you will get out of the application. A clearer understanding of the long term technical roadmap. What does ArchivesSpace look like in the next year? Five years? Is there a strategy for making the public interface more "modern", i.e. progressive enhancement. Data Cleansing. I could have used help trying to load the fast topical headings into the system How locations and containers would develop. Cleanup data BEFORE importing. ArchviesSpace staff interface is not user friendly for bulk editing data, unlike XML editors; when I do imports of individual EADs now, I try to clean up as much as I can before importing.
| ||
Happy hour / mixer | |||
Lunch on your own? |
| ||
Registration form |
| ||
5 min | Next meeting |
|
...