-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jupiter: Thesis Deposit #709
Comments
Thanks @weiweishi |
thanks @sfarnel So I just wanted to clarify. |
Thanks @weiweishi @leahvanderjagt can confirm whether or not a St. Stephen's would ever come not in a batch. Perhaps not! |
Confirmed with @leahvanderjagt that admin should be able to deposit into both FGSR and St. Stephen's College community and their collections. |
Is there a defined list of required fields for thesis on the form? According to here the properties that are required in the data dictionary: It's basically just
I would have assumed language, subjects & keywords, license & rights (even though every thesis has the same license), and Abstract/description (as this is indicated on the mockups) to be required? Then assuming the rest are optional (degree/department/supervisor/etc) Can anyone give some clarification here? Thanks! |
This is exclusively for the thesis deposit form. So they will only fail validations when creating a new thesis or editing an existing thesis (forcing a user to update old thesis to match new requirements, aka add an abstract/language/etc) via thesis deposit form. So if this might prove to be a problem then better to make these optional in the thesis deposit form. |
So the validation will only be enforced on the UI, not on the data model level? This is probably different from the original meaning of the "required" in the data dictionary. Thanks for the clarification. My impression is this might be an issue for editing old thesis? when if we want to add/edit some info on these old theses but don't have all the required info? @leahvanderjagt how often do you see the old ProQuest theses to be modified through the UI? My sense is it doesn't happen often but does happen occasionally in the past, for an author name change etc. How important do you feel we should have validation on the thesis deposit form for admin, to make sure new deposit has all the required information we need? |
According to data dictionary, there will be two additional date fields, Date Accepted and Date Submitted will be on the deposit thesis form? Is this correct? |
Thanks @murny and @weiweishi for this discussion! When we worked this out with @leahvanderjagt she wanted the number of required elements to be very minimal for the form because theses rarely get deposited in this way, and when they do we often have very little information, as you've observed. This was hashed out in a meeting and info is in ualbertalib/metadata#125 and the data dictionary. @murny those two fields are on the form but optional. Hope this helps! |
Deployed to production. Demo-ed to @abombak . Will close this ticket. |
Requirements:
https://github.com/ualbertalib/metadata/blob/master/data_dictionary/profile_thesis.md
and St. Stephen's community/collections
"This thesis is made available by the University of Alberta Libraries with permission of the copyright owner solely for non-commercial purposes. This thesis, or any portion thereof, may not otherwise be copied or reproduced without the written consent of the copyright owner, except to the extent permitted by Canadian copyright law."
Wireframes:
https://jupiter.mybalsamiq.com/projects/jupiter/Deposit%20-%20Thesis
The text was updated successfully, but these errors were encountered: