| Description: | ETD document submission: security and consistency | ||
| Projects: | ETD | ||
| Priority: | 99 | Task ID: | 118 |
| Long Description: | Scott Eldredge points out that we may have some type of a consistency and security issue. How do we know that the document submitted to this system is the one approved by the committee? | ||
| Status: | Hold | ||
| Owner: | Hold, Unowned | Contributors: | |
| Due: | TBD | Opened: | 3/18/2002 |
| Changed: | 8/18/2004 | ||
| 4/5/2002 | This is a current problem with the printed documents too. There is no guarantee that the document reviewed by the committee is the one submitted by the student to the graduate office and library. Because there is no current process to manage this for printed documents. We are going to move this issue to a future release. | ||
| 8/9/2002 | This was not added to the 2.0 project. | ||
| 6/24/2003 | There are a number of issues here. If we just look at the submittal process, how do we know that the person submitting the document is who they say they are? Is the NetID sufficient authentication for us to believe this? Do we need to keep a log of transactions and do we need to secure the log? How do we know that the document in CONTENTdm is the one that was submitted? | ||
| 11/14/2003 | This issue will be partially addressed in version 3. The submittal process requires a NetID to login and the system runs under SSL. The document submitted will be reviewed by the college graduate secretary (or whoever is tasked with administering ETDs for the college) at which point there should be some validation that the item submitted is the one approved by the college. This item will not be closed at this time since I would like to also address system security, encryption, and document validation in a future release. | ||
| 1/13/2004 | Adobe Acrobat 6 has features for signing a document. Take a look at this for a future release. | ||
| Description: | Login and review process for thesis committee | ||
| Projects: | ETD | ||
| Priority: | 99 | Task ID: | 381 |
| Long Description: | Create a login and pages for the graduate student’s committee to review the ETD Metadata and ETD file (PDF) for committee approval. Don’t allow the ETD to be submitted for Administrative Approval (college level) until at least the committee chair has approved the ETD on-line. If any committee member has not completed the on-line approval of the ETD, display a warning message if the student prematurely submits the ETD for administrative approval.
Will need to key off of the committee members so they are authorized to access only their student’s ETDs for review and committee approval. May want to have a button in the student view for sending out e-mail notifications to the committee members informing them that the ETD is ready for committee review and approval. When each of the committee members have completed their review and approval of the ETD (with comments for corrections that must be made to the ETD content) generate an e-mail message to the student informing that the specific committee member has completed the review and approval. | ||
| Status: | Hold | ||
| Owner: | Hold, Unowned | Contributors: | |
| Due: | Version 4 | Opened: | 3/3/2003 |
| Changed: | 8/19/2004 | ||
| 7/15/2003 | The project committee determined that there is more organizational ground work which needs to be done before this task can be acted upon. It will not be included in version 3. | ||
| 8/19/2004 | Selby Herrin reported that using the ETD system for commitee review of a thesis is not supported by the administration at this time. | ||
| Description: | Investigate alternatives to internal coding of the ETD system. | ||
| Projects: | Documentum, DSpace, ETD | ||
| Priority: | 99 | Task ID: | 581 |
| Long Description: | Two products may provide similar features to the ETD system: DSpace and Documentum. We should investigate for release 4 whether either of these should be selected instead of coding our own project. | ||
| Status: | Hold | ||
| Owner: | Hold, Unowned | Contributors: | |
| Due: | Version 4 | Opened: | 12/12/2003 |
| Changed: | 8/19/2004 | ||
| 8/19/2004 | DSpace is not an appropriate product. Although it supports a workflow, it is quite restricted and not as flexible as this project requires, at least as BYU has defined it. Documentum is still an unknown. At the point that Documentum is available to us, we will investigate its usefulness as an ETD tool. | ||
| Description: | ETD Project Meetings | ||
| Projects: | ETD | ||
| Priority: | 9999 | Task ID: | 717 |
| Long Description: | Attendance and topics for ETD project meetings. | ||
| Status: | Hold | ||
| Owner: | Eldredge, Scott | Contributors: | |
| Due: | TBD | Opened: | 4/26/2004 |
| Changed: | 3/9/2005 | ||
| 8/18/2004 | Scott Eldredge, Selby Herrin, Carla Kupitz, Jacob Jenson, Bill Lund | ||
| 8/30/2004 | Sarah Warburton, Jacob Jenson, Scott Eldredge, Wendy Duran, Selby Herrin, Carla Kupitz, Bill Lund, Kayla Willey - Began project definition. | ||
| 9/1/2004 | Selby Herrin, Sarah Warburton, Jacob Jenson, Scott Eldredge, Bill Lund, Wendy Duran, Carla Kupitz, Mindy Swanson - Continued project definition. Next meeting 9/7. | ||
| 9/27/2004 | Jacob Jenson, Carla Kupitz, Wendy Duran, Selby Herrin, Scott Eldredge, Bill Lund | ||
| 11/18/2004 | Project management turned over to Scott Eldredge. | ||
Version: 4.0
©BYU 2002, 2003, 2004