Moira Fitzgerald
My feedback
32 results found
-
13 votesMoira Fitzgerald
supported this idea
·
-
12 votesMoira Fitzgerald
supported this idea
·
-
6 votesMoira Fitzgerald
supported this idea
·
-
1 voteMoira Fitzgerald
shared this idea
·
-
2 votes
An error occurred while saving the comment Moira Fitzgerald
supported this idea
·
-
14 votespartially released ·
AdminKatie Gillespie
(Special Collections & Archives Program Manager, Atlas Systems, Inc.)
responded
Aeon 5.1 added the unlimited custom fields feature but did not increase field sizes.
An error occurred while saving the comment Moira Fitzgerald
commented
Hi, along these lines, one of our archivists, Mark Custer, told me it would be possible for our IT staff to add additional fields to the Aeon database. Has anyone ever done this?
Moira Fitzgerald
supported this idea
·
An error occurred while saving the comment Moira Fitzgerald
commented
One piece of information we'd like to store is fellowship information, since one of the reports I have to run is on how many of our reading room visitors are on a fellowship. We use UserInfo3 to record that. Our Manuscripts & Archives repository uses UserInfo1 and UserInfo2 to record information about permissions that researchers have to view special collections. One way to approach it might be to have more "user defined" fields, since it will be hard to predict what everyone would want. As we add more reading rooms at Yale we're seeing that everyone has information they'd like to track and we're running out of fields to use, and yet there are some fields that we just don't need. Also, as we work with different campus systems, I could imagine possibilities where we could import things like student majors/programs, class year, graduate vs. undergraduate, etc.
For us the transactions table is more critical. Again as we add more reading rooms we're finding that different pieces of information stored in the MARC record or finding aid that are critical for paging or things we would want to run reports on. Examples include restrictions, notes fields that include size and locations, etc. Again we're running low on iteminfo fields, so having more of those would help, while fields like ISXN and MaxCost just aren't relevent. I think the recently released SAA-RBMS guidelines could also be consulted, as they recommend some standard pieces of information.
Perhaps as this discussion thread continues, a conversation could also be held at the XPSU conference next month?
Thanks!!!
An error occurred while saving the comment Moira Fitzgerald
commented
Hi. We currently use one of the UserInfo fields to record fellowship information, as we have to report how many of our readers each year were on a fellowship from our library. Other sites on campus use UserInfo2 and UserInfo4 to record if patrons have permissions to view certain collections. I could see the benefit to having dedicated fields for those purposes, as opposed to fields for fax number, date of birth, or even delivery method. Thanks.
An error occurred while saving the comment Moira Fitzgerald
commented
Hi,
Are there any plans to modify or add fields in the Aeon database?. Many of the fields seem to be copied over from ILLiad, like MaxCost in the transactions table, which I can’t imagine many special collections places would use. Or just outdated, like fax in the users table. I ask this because we would like to import more information from our catalog records into Aeon, and we are already running low on iteminfo fields. It seems like it would be a good idea to review those fields with the user community to see what people need.
Thanks!
Moira
-
51 votes
An error occurred while saving the comment Moira Fitzgerald
commented
Hi, This is something we desperately need as well now that we are managing items that could be at any of three locations. While we're waiting, has anyone experimented with routing rules to do this? Thanks!
Moira Fitzgerald
supported this idea
·
-
45 votes
An error occurred while saving the comment Moira Fitzgerald
commented
Hi, I like this idea, but it would be nice if the rule could take into account the last time the patron was in the reading room. So patrons can work on materials for months and if they are coming in regularly then it's not a problem for us to keep things on hold for that long. We have a custom report that provides a list of items where the requester hasn't been signed in for over a week. Then we manually remove those items from the hold shelf. Thanks.
Moira Fitzgerald
supported this idea
·
-
7 votesMoira Fitzgerald
supported this idea
·
-
12 votesMoira Fitzgerald
supported this idea
·
-
2 votesMoira Fitzgerald
supported this idea
·
-
8 votesMoira Fitzgerald
supported this idea
·
-
6 votesMoira Fitzgerald
supported this idea
·
-
2 votesMoira Fitzgerald
supported this idea
·
-
3 votesMoira Fitzgerald
supported this idea
·
-
18 votesMoira Fitzgerald
supported this idea
·
-
1 voteMoira Fitzgerald
supported this idea
·
-
21 votesMoira Fitzgerald
supported this idea
·
-
12 votesMoira Fitzgerald
supported this idea
·
-
10 votesMoira Fitzgerald
supported this idea
·
We're going to have to use the "Special Request" field, most likely, and also change our form that is used for Orbis to use that field instead of the notes field, so the information is all going to one place consistently. But being able to use the notes field would be easier. Thanks.