Page 4 of 17. Showing 167 results (0.02 seconds)
Admin UI - Configure hidden communities and collections
the restriction on the "Default read access" role. Anonymous users can now see the collection and view associated items. uc-end-user uc-admin uc-access … Title (Goal) Configure hidden communities and collections that will not be visible to users without access Primary Actor System | Human | External SystemStructure - Apply licenses to bitstreams
-admin uc-end-user uc-deposit uc-content-model uc-relationships … Title (Goal) License on bitstream Primary Actor System | External System | End User | Administrator Scope Level Story (A paragraph or twoGive Collections/Communities short names/acronyms
allow access to the full name. uc-analysis-needed uc-end-user uc-admin uc-content-model … Title (Goal) Improve Users experience when displaying item location data Primary Actor Administrator Scope Level Story (A paragraphIntegrations - Streaming Image Server
Title (Goal) Management of Images via DSpace Primary Actor System | External System | End User | Administrator Scope Level Story (A paragraph or two describing what happens) uc-integration uc-user-experienceAdmin UI - Aids and tooltips in the UI
by systems that provide very limited labels, and where it is unclear what happens if a certain button is pushed. uc-admin uc-user-experienceAdmin UI - Simplify Collection Creation Based on Template
Title (Goal) Admin UI - Simplify Collection Creation Based on Template Primary Actor End User | Administrator Scope UI / command line Level … so system admins can script duplication or even bulk duplication. uc-user-experience uc-structure uc-admin uc-content-modelStructure - Check Bitstream names against allowed file name pattern
Title (Goal) Check Bitstream names against allowed file name pattern Primary Actor End User | Administrator Scope Level Story (A paragraph … of the institutions naming standard. uc-structure uc-user-experience uc-configuration uc-depositStructure - Generated provenance for all added bitstreams
what happens) Provenance information is generated for submitted (manual or batch) items/bitstreams as well as added/removed bitstreams. Example: A user adds a new bitstream to an item. User does not want to manually create new provenance information (action, user, date, # of bitstreams, file names, bytes, checksumsStructure - Generate technical metadata per bitstream
Title (Goal) Generate and store/display technical metadata per bitstream Primary Actor System | External System | End User | Administrator Scope … manual or batch submission, as well as files added to existing items). uc-structure uc-integration uc-admin uc-metadata uc-preservationAdmin UI - Permissions of a new user in an eperson group
Title (Goal) Permissions of a new user in an eperson group Primary Actor Administrator Scope Level Story (A paragraph or two describing … created a group "Students" which has READ and WRITE privileges on the thesis collection. In order to give Susan the permissions she requires, John adds her user