What do you all think? Is it enough? Should we also link to the museum? Is there a significant risk that the museum will someday make changes to its site that break that URL? Is it worse to provide less information up front or to risk having potentially outdated information in our records that we'd have to contend with later (if this was a professional project)?
I'll note here that there is a variation where we just embed the link into the Rights statement. However, when I did this I noticed that the linked text was noticeably lighter than the rest of the statement. I'll paste snips of the two variations below so you can all judge the aesthetics.
Label
Rights
Element Description
This element states the various property rights associated with the resource, including intellectual property rights.
Required?
Yes
Repeatable?
Maybe
Guidelines for Creation of Content
Use the following statement:
All rights reserved by the University of Alabama. Permission to reproduce in any format must be requested in writing by contacting the Paul W. Bryant Museum.
This is the HTML that could go in the second Rights field:
<a href="http://bryantmuseum.ua.edu/direction.cfm?dir=contact" target="_blank">Contact the Paul W. Bryant Museum</a>
Examples
All images use the exact wording and HTML code above.
Notes
The Rights statement may be pasted directly into Omeka. To make the second Rights field, you need to paste in the HTML code and check the "Use HTML" box.
I like the wording better on the second example, but definitely see what you mean on the lighter hyperlink. Also, as far as the hyperlink goes, from a user standpoint, I think the hyperlink would be helpful, but as you point out, the link breaking is a concern. I don't know if it's enough of a concern to be a deterrent though.
ReplyDeleteThis looks good! So a couple of thoughts, this may be silly but if we use the second version might some user not understand that the text was a hyper link? And if they were unfamiliar would the wording in the first version be any clearer? I'm not sure, but I think the second version is a little cleaner. Also, when I was looking at digital repositories I saw several records included links when dealing with rights management. They just linked directly to the corresponding pages and didn't even state who or what institution was to be contacted in the record.
ReplyDeleteGood work and comments!
ReplyDeleteFirst off, it's good to have to separate data entry boxes. If you go to an example data entry form in Omeka, you'll see that I added additional Rights element options by extending our instance from Simple Dublin Core to Qualified Dublin Core.
Also Omeka provides a "drop down" box for repeated data entry tasks (see what Damen has already done for his "Spatial Coverage" element). It's call "Simple Vocab" and your vocab would include just one option. Here are the instructions, though you may wait until tonight to hear my discussion about this functionality option.
1) go to our Omeka instance and log in
2) click on “Simple Vocab” option on left nav bar
3) Select your element from the drop down Element list (middle of the page top)
4) enter the list of vocab options in the big empty box as directed
5) click big green “Add/Edit Vocabulary” button when done (note that you can always come back and edit the list as needed.
The only problem with the Simple Vocab option is that you won't be able to embed a live hyperlink (which Amy didn't like anyway! :-) ... if you still want to use the Simple Vocab option, then you'll need to spell out either an email address or web URL.
One last question? In what circumstances would this element be optional?