kimisgold / omeka-s-wireframes Goto Github PK

Multiple media items can be added at one time. Each media item can be one of any number of media types. For now we plan on adding the following media types:

• File
  • file upload interface
  • drag and drop interface
• Image (embedded as an img)
  • URL (text input)
• YouTube (embedded as an iframe)
  • URL (text input)
• Flickr (embedded as ???)
  • URL (text input)

Edit: removed width and height inputs until we can figure out a way to handle dimensions.

• The page title should be in the singular, "Import Vocabulary"
• Due to a bug in EasyRdf users can't import via URL
• Instead of "Upload a file", a more accurate phrase is "Import from file"
• We will only accept the following formats: "RDF/XML" and "N-Triples"
• Users should set the file format
• Users should set the "namespace URI", a text input
• Users should set the "prefix", a text input
• Users should set a "label", a text input
• Users should set a "comment", a textarea

• On user add, consider putting every field on one page (to avoid incomplete forms)
• Remove password altogether from user add in favor of email confirmation (TBD)
• On user edit, move password fields to a separate tab
• On user edit, the "Metadata" tab should be "Profile"
• Remove the specific permissions in the "Permissions" tab until we determine what global permissions will be available

• "Metadata" tab should be "Values"
• "Files" tab should be "Media" (we'll discuss this tab in a separate issue)
• "Class" should be something like an optgroup support select (optgroup is the class's vocabulary)
• "None" is not a valid "Class" anymore
• The default "Class" is "Resource" ("RDFS" vocabulary)
• The "Text" type should be able to accommodate any form element
• Look into using Chosen (see above) to implement property selection
• Users will not be able to edit property labels
• Add a "public/not public" flag
• Add a "shareable/not shareable" flag
• Add an "item set" multiple selection
• Removing a property should open an "Are you sure?" prompt

• Remove "Edit selected items" button
• "Name" header should be "Title"
• "Type" header should be "Class"
• Remove "Creator" header for now
• Clicking the item title goes to item/show
• Clicking the edit icon goes to item/edit
• Remove the view icon
• Clicking the view more icon opens a quick view (TBD)

(cc: @jimsafley, @zerocrates, @kalbers, @patrickmj)

Check out the 'topbar' branch to see the latest vision of what fixed user bars, section navigation, and save button areas would look like. The 'items/add' view is going to be the best one to look at. Provide feedback here at your convenience.

It's important to note that properties aren't directly assigned to classes, rather they are assigned via an intermediary "property set". Like so:

• Class_1 ("Agent")
  • Propery_Set_1 ("Custom Agent 1")
    • Property_1 ("Name")
    • Property_2 ("DOB")
  • Property_Set_2 ("Custom Agent 2")
    • Property_1 ("Name")
    • Property_3 ("Nickname")

Also, properties assigned to property sets can have a custom "alternate label" and "alternate comment" that are specific to that assignment. In the example above, "Name" may be customized to "Full Name" for Property_Set_1 only. There should be some way to manage these alternate fields for every property set.

Currently, the various submit buttons across the administrative interface are specific about what they do (e.g. "Create Item", "Import Vocabulary", "Add User"). Instead, should they simply say "Submit"?

• For consistency across the interface
• To avoid confusion with their respective headlines