Skip to end of metadata
Go to start of metadata

This wireframe is...

Details

Jira

Fix for

not implemented

Hierarchy needs to be implemented

CSPACE-3191

v1.6

3 Comments

  1. Walkthrough with Joe King, the Walker

    Comments

    • If a room has a thousand shelves, how does one enter information or transfer information from the existing database?
    • At the Walker, the storage locations of the objects (down to the shelf level) are tracked using RFIDs.
    • "All location information is imported from the RFID  - if I move an object and scan the barcode, then the new location information is then inputed into the system."
    • The Walker does not have a list of storage location authorities to choose from. The location information is kept in a related database, and everytime an object is moved, a record is created in that database. The current location can be viewed from the object record, but if you want to view the history of locations, you'd need to bring it up in the related database.
    • The location is entered (automatically via RFID) in two fields: Room (e.g. Main storage, Art storage, etc.), and Shelf (e.g. T43a, T43b, etc. where T43 is the unit and a/b is the shelf). So a full description of an object location would be Art storage T43a.
    • Date stamp (of when it was moved to the location) and the identity of the person who put it there are also kept.

    Re: Hierarchy Display

    • "I like the one on the top better, with the horizontal view. It' a little easier for me to navigate."
    • Are you a mac user? "Not currently. I've had them in the past. Is it because the top one looks like mac? I work on a PC but the top one is easier to follow. Makes more sense."
  2. Walkthrough with Kim and Kirsten, SMK

    Re: Hierarchy Display

    • Kim: I think it makes sense, definitely.
    • Kirsten: A bit more detailed than the most of (the systems I've used)
    • Kim: Tree navigation is closer to what we have today. We are quite familiar with that way of navigating.
    • Kim: Somehow I think the one on the top is a bit more clear. But it seems to take up more space, doesn't it?
    • Kirsten: If I enter "Shelf 4B", then would I be asked, "is it Bay 1, 2, 3, or 4?" Is it possible to choose which one? With a new object, you again need, Shelf 4B. will you then be asked, is it Bay 2, or Bay 3? (A: The children records are created from the parent record. The display name shows the whole branch (e.g. MST:2:4B) rather than just the record itself (e.g. Shelf 4B).
    • Kirsten: For the Location name field, it would be nice to be able to type as little as possible i.e. "Shelf 4B" instead of the whole branch. The user would remember the hierarchy in their head. For me, it's very good to pick from the hierarchy view instead of typing.
  3. Walkthrough with Joe King, the Walker

    Comments

    • Understood the hierarchy fields. Broader context - all of the shelves, Equivalent context - other similar storage units, Narrower context - if you chose a particular shelf.
    • Is it possible to have fewer levels in the hierarchy? At the Walker, only need name of the room, and shelf or screen
      • e.g. Art storage (room) : T43 (shelving unit) : C (shelf within the unit)
      • e.g. Painting storage (room) : Screen 25 (screen) : B (of 2 sides, A and B)
    • Is it possible to have different naming convention in the hierarchy?
    • Currently uses a related database for location. The location field appears within the cataloging record.
    • Currently does not use name authority. Artist names go in one field, which is problematic, because it first and last names, and sometimes multiple names get put into one text field. Name authority would definitely be helpful.
    • Location of "related materials" (e.g. light bulbs, specific projector to install and display artwork) need to be kept. 
    • Media-based artworks: multiple generation of the same work, master copy (kept) vs. exhibition copy (DVD, consumable)