Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • When should a non-collection object be a direct child of a collection object?
    • Should/can the model be different from what the UI will display?
      • items will not always belong to sets
        • MO: Yes, I imagine that model will need to support items that have not yet been assigned to a set.
      • items could be children of more than one set
        • MO: Yes, I image a use case where an item can belong to more than one set, not sure we need to support this right now though.
      • sets can be children of other sets
      • example: :  MO: Yes, the model will at some point need to support this, but not sure we need it for demo**** collection A  has:
          • set B
            • item 1
            • item 3 (also in set C)
          • set C
            • item 4
            • item 3  (also in set B)
          • set D
            • set E
              • item 5
          • item 2  (not in a set)
    • Is there a reduced case of the tree for the Hypatia Oct 31 deadline that can simplify our discussion?
  • Can an object be a direct child of more than one Collection?  (assuming no at the present)
    • MO: Correct, assume no for now although in the future we will probably want to revisit this in our data models
  • Should we be dealing with any permissions issues?
    • edit permissions for objects?  (if so, time for some fixture users ...)
      • MO: ideally, meaning time permitting it would be useful to have some examples of how the application would support multiple levels of permissions (archivists, superuser, etc.)  I am not sure what Jessie's current edit workflows support so we should discuss.  As a bare minimum  We should talk to UVA as it would be nice to have a botton in theplace holder on the home page called something like Administration where one would go to edit permissions.
    • editing of edit permissions in the UI?

...

  • ok to skip loading disk image files themselves (for user download) except for xanadu? I'm told they aren't for the public ...
    • MO: For the time being yes.  Ideally, if time permits it would be nice to load the Gould disk images too as I believe all of these can be made public but this isn't critical due to time limitations.
  • leave out elements with no value?
    • MO: I believe so, yes.

HOME Screen Text:

MO: Here is a stab at explanatory text for the application at the very bottom left of the home page.

Hypatia is demonstration Hydra application (Fedora, Hydra, Solr, Blacklight) that will support the acessioning, arrangement / description, delivery and long term preservation of born digital collections. Hypatia is being developed as part of the AIMS Project ("Born-Digital Collections: An Inter-Institutional Model for Stewardship"), funded by the Andrew W. Mellon Foundation.  Arrangement and description functionality is not fully supported in the current demonstration application.For more information on the Hydra Project please see http://projectHydra.org/Image Removed.