Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Building Blocks (~30 min)

collection types

  • nesting
  • branding
  • multiple-membership
  • creator/manager permission

admin sets

  • workflow
    • 1 step
    • mediated work flow
  • visibility
    • embargo
    • leases
    • public | private | institution
    • visibility as policy
      • students submitting DTD cannot embargo
      • temporal permissions to materials

collections



work

  • work types
    • one work type to do everything
    • resource type
    • submission tool to get stuff of a certain kind
  • nested works - parent and child works
  • filesets (vs. using nested works)


How to use admin sets as policy objects

Use Cases (~1 hour)

Pick 4 uses cases

  • design 2 as separate systems
  • design 2 in one system

Have a use case you are working with that you would like to explore?  Add it here.  A variety of use cases will be selected to serve as examples during the workshop.  We will work through design possibilities and questions during the workshop in order to build a better understanding of the tools we have available to architect our repositories.

Use Case: Self-Deposit

In a self-deposit repository system, any user with a login can add works and files.

  • As a logged in user, I want to create new works that are attributed to me and discoverable by the public.
  • As a logged in user, I want to be able to organize my works for my own use.
  • As a logged in user, I want to be able to organize works to share with others.

Use Case:  Curated Exhibits

In a curated repository, select staff can create content and selectively release it for public consumption.

  • As a librarian, I want to select public works to include in a curated exhibit.


Use Case: Mediated Deposit and ETDs

Use Case: Research Data Curation


Use Case: Migration from D-Space to Hyrax

There are many uses for D-Space.  One use is the collection of faculty/staff research for a department on a university campus.

  • As a repository manager, I want to create collections for each organizational unit of the university.
  • As a faculty/staff member, I want to be able to create new works within my department's collection which are attributed to me.

Use Case: Art Institute of Chicago


Use Case: Journals & Volumns



Use Case: ... feel free to add another use case


Approaches to System Design

Institutional Repository

  • How items come into a system?  May have multiple workflows to support many different purposes.


Digital Collection

  • Fewer people working with the system.
  • More homogenous workflow.

Separate systems vs. one large system. 

  • Homogeneous Content
  • Various of content

Hands On Activity (~30) 

Using your own use cases or ones we supply, design an approach

Group Discussion (~30)



Common Customizations to Application Flow

There are several major customizations to flow that I have seen at various institutions.  We could approach it from there.  For example…

  • self deposit - start from uploading a work of any type; often using only a single work type
  • file oriented - start by selecting the type of file being uploaded which drives work type options, workflow, collections the work can go into
  • workflow oriented - start by selecting a workflow
  • collection oriented - start by selecting a collection (e.g. ETD, exhibit, etc.) and what happens next depends on what you selected

The first one is the only one supported out of the box without customization.







  • No labels