Lee Library Information Systems Task List
Family Histories Archive

Description: Review metadata requirements for Family Histories Archive
Projects: Family Histories Archive
Priority: 50 Task ID: 769
Long Description: The project team needs to determine the metadata requirements for the archive, paying special attention to defining the source of the metadata, and defining manual processes.
Status: Open
Owner: Willey, Kayla Contributors: Jenson, Jacob
Due: TBD Opened: 6/16/2004
Changed: 9/27/2004  
6/16/2004 The first meeting is being held on 7/2 at 10:00 AM in the LiS conference room. I've requested a list of the metadata, whether each item is required, what its source is, and whether it uses controlled vocabulary.
8/17/2004 Kayla has provided the metadata requirements, which are documented at http://as3.lib.byu.edu/projects/FHA/Documents/FHA%20Metadata.pdf.

I need the project team to give final approval to this before closing this action item.

8/31/2004 The project team approved the metadata.
Description: Define look and feel for Family Histories Archive
Projects: Family Histories Archive
Priority: 99 Task ID: 770
Long Description: The look and feel for each of the screens defined in the workflow needs to be established. This is a prerequisite to the early usability testing.
Status: Open
Owner: Lesue, David Contributors: Jenson, Jacob
Due: TBD Opened: 6/16/2004
Changed: 8/17/2004  
7/15/2004 I've asked Randy whether it would be possible to solicit help from CID for this.
7/26/2004 Larry Seawright from CID has been added to the project.
8/17/2004 Jacob Jenson, David Lesue and Bill Lund met with Larry Seawright from CID regarding the user interface. Jacob will be incorporating the changes he suggested. This item will be closed when the first phase of usability testing is completed on the submission user interface.
Description: Define and complete the search interface usability testing on i/f design.
Projects: Family Histories Archive
Priority: 99 Task ID: 771
Long Description: The Family Histories Archive search interface needs to be tested for usability using the designed interface before implementation. If the testing identifies problems, they need to be resolved before design is complete.
Status: Open
Owner: Eldredge, Scott Contributors: Hunter, Mike
Jenson, Jacob
Lesue, David
Due: TBD Opened: 6/16/2004
Changed: 11/18/2004  
7/15/2004 I've asked Randy whether it is appropriate to ask CID for help with this.
7/26/2004 Larry Seawright has been added to the project.
Description: Define and complete the submission interface usability testing on i/f design.
Projects: Family Histories Archive
Priority: 99 Task ID: 772
Long Description: The Family Histories Archive submission interface needs to be tested for usability using the designed interface before implementation. If the testing identifies problems, they need to be resolved before design is complete.
Status: Open
Owner: Eldredge, Scott Contributors: Hunter, Mike
Jenson, Jacob
Lesue, David
Due: TBD Opened: 6/16/2004
Changed: 11/18/2004  
7/15/2004 I've asked Randy whether it is appropriate to ask CID for help with this.
7/26/2004 Larry Seawright from CID has been added to the project.
10/6/2004 Mike Hunter will provide 10 names and contact information for the usability test. The first test will be unscripted for five people. The goal will be to generally hear from them about the system. The second test will be scripted.
Description: Define support paths for Family Histories Archive
Projects: Family Histories Archive
Priority: 99 Task ID: 773
Long Description: We need to define the supports paths for all classes of users of the Family Histories Archive.
Status: Open
Owner: Eldredge, Scott Contributors:
Due: TBD Opened: 6/16/2004
Changed: 11/18/2004  
6/16/2004 Currently the users are defined as: administrative, submission, searching.
8/17/2004 The project team will begin this on 8/31/04.
Description: Define required web-browser plug-ins
Projects: Family Histories Archive
Priority: 99 Task ID: 774
Long Description: We will not require "unusal" browser plug-ins. We will document here the required plug-ins, if any.
Status: Open
Owner: Eldredge, Scott Contributors:
Due: TBD Opened: 6/16/2004
Changed: 11/18/2004  
9/27/2004 At this point the only required plug-in is Adobe Acrobat. We need to determine the lowest version number that will be supported.
Description: Define usability goals for the search and submission interfaces
Projects: Family Histories Archive
Priority: 99 Task ID: 775
Long Description: The usability goals for the Family Histories Archive need to be defined before testing. The goals need to include the expected users of the system, expected technical competence, and expected tools available to the end user. Note that it may be possible to define different goals for the search and submission interfaces.
Status: Open
Owner: Eldredge, Scott Contributors:
Due: TBD Opened: 6/16/2004
Changed: 11/18/2004  
7/15/2004 I've asked Randy whether it is appropriate to ask CID for help with this.
7/26/2004 Larry Seawright has been added to the project.
Description: What versions of Adobe Acrobat will be accepted?
Projects: Family Histories Archive
Priority: 99 Task ID: 778
Long Description: The project team needs to define the versions of Adobe Acrobat documents that will be accepted into the Family Histories Archive. This may affect support, documentation, training, and coding.
Status: Open
Owner: Eldredge, Scott Contributors:
Due: TBD Opened: 6/16/2004
Changed: 6/16/2004  
6/16/2004 We know that there are some backward compatibility issues with Adobe Acrobat Reader 4 trying to read an Adobe Acrobat version 6 file which has not been properly prepared. Should we define a version of Adobe Acrobat Reader that searcher must have in order to view the contents?
Description: Owner for Family and Church History Library tasks
Projects: Family Histories Archive
Priority: 99 Task ID: 781
Long Description: There currently is no owner for deliverable 10.1, putting a link on the Church's FamilySearch.org website, and for deliverable 10.8 publicity originating at FCH.
Status: Open
Owner: Eldredge, Scott Contributors:
Due: TBD Opened: 6/18/2004
Changed: 11/18/2004  
Description: Set-up Initial Usability Testing
Projects: Family Histories Archive
Priority: 99 Task ID: 796
Long Description: Perform usability testing at the front-end of the Family Histories Archive Submission System project. This is to guide us during the development of the user interface. To complete this task the user interface mock-up needs to be completed, the target audiences defined, and up to 15 test participants identified.
Status: Open
Owner: Eldredge, Scott Contributors: Seawright, Larry
Due: TBD Opened: 8/17/2004
Changed: 11/18/2004  
8/17/2004 We met with Larry Seawright today and determined that we will do two phases of usability testing at this stage. There will be no more than 5 tests during which there will be interactive dialog with the test subjects regarding the interface. Then there will be no more than 10 tests which are scripted.
Description: Discuss FHA project with the Church
Projects: Family Histories Archive
Priority: 99 Task ID: 842
Long Description: Randy Olsen would like for us to discuss the Family Histories Archive project with the Church Family History Library.
Status: Open
Owner: Olsen, Randy Contributors:
Due: TBD Opened: 9/30/2004
Changed: 9/30/2004  
9/30/2004 There appears to be a disconnect between the Church's understand of the family history retrospective project and the family histories archive submission system project. Randy will schedule this.
Description: Post collection guidelines for family histories
Projects: Family Histories Archive
Priority: 99 Task ID: 844
Long Description: Mike Hunter has printed guideliness for family histories. He will provide a copy that will be posted on the project web site.
Status: Open
Owner: Hunter, Mike Contributors:
Due: TBD Opened: 10/8/2004
Changed: 10/8/2004  
Description: Will the Family History project be ADA compliant?
Projects: Family Histories Archive
Priority: 99 Task ID: 845
Long Description: Will we add ADA accessibility to this project?
Status: Open
Owner: Eldredge, Scott Contributors:
Due: TBD Opened: 10/8/2004
Changed: 11/18/2004  
Description: Family Histories Archive Project Meetings
Projects: Family Histories Archive
Priority: 9999 Task ID: 735
Long Description:
Status: Open
Owner: Eldredge, Scott Contributors:
Due: TBD Opened: 5/28/2004
Changed: 11/18/2004  
6/15/2004 Bill Lund (LIS), Jacob Jenson (LIS), Dennis Meldrum (Church Family History Library), Joe Everett (Church Family History Library), Scott Eldredge (HBLL), Betty Walling (OIT), Mike Hunter (HBLL), Kayla Willey (HBLL), David Lesue (HBLL)
6/30/2004 Scott Eldredge (HBLL), Mike Hunter (HBLL), Jacob Jenson (LIS), Bill Lund (LIS), Kayla Willey (HBLL) - Establish workflow
8/17/2004 Jacob Jenson, David Lesue, Bill Lund, Larry Seawright (CID) - User interface.
8/31/2004 Kayla Willey, Joe Everrett, Scott Eldredge, Jacob Jenson, Mike Hunter, Betty Walling, Bill Lund
11/18/2004 Project management turned over to Scott Eldredge.
Description: Implement the use of non-Roman languages in the Family Histories Archive
Projects: Family Histories Archive
Priority: 99 Task ID: 761
Long Description: Currently the only languages supported in the Family Histories Archive will be Romanized languages. The project team would like to support non-Romanized languages for the documents. Whether this extends to the metadata is not determined.
Status: Hold
Owner: Hold, Unowned Contributors:
Due: TBD Opened: 6/16/2004
Changed: 6/16/2004  
6/16/2004 Identified during the project definition for release 1 as a future need.
Description: Integrate logon using the Family Search ID
Projects: Family Histories Archive
Priority: 99 Task ID: 762
Long Description: The first release of the Family Histories Archive used the BYU NetID for authentication. The project team would like to integrate with the Church's Family Search ID in a future release.
Status: Hold
Owner: Hold, Unowned Contributors:
Due: TBD Opened: 6/16/2004
Changed: 6/16/2004  
6/16/2004 Identified during the project definition for the first release.
Description: Accept additional text types in Family Histories Archive
Projects: Family Histories Archive
Priority: 99 Task ID: 763
Long Description: The first release of the Family Histories Archive only accepts PDF documents. The project team would like to include other document types in the future.
Status: Hold
Owner: Hold, Unowned Contributors:
Due: TBD Opened: 6/16/2004
Changed: 6/16/2004  
6/16/2004 Identified during the project definition for the first release. Document types discussed are raw ASCII text, MS Word, and Corel WordPerfect.
Description: Accept streamed media in the Family Histories Archive
Projects: Family Histories Archive
Priority: 99 Task ID: 764
Long Description: The project team would like to see the Family Histories Archive accept streamed media (sound, image).
Status: Hold
Owner: Hold, Unowned Contributors:
Due: TBD Opened: 6/16/2004
Changed: 6/16/2004  
6/16/2004 Identified during the project definition for the first release.
Description: Link the Family Histories Archive to the Church Family History Catalog
Projects: Family Histories Archive
Priority: 99 Task ID: 766
Long Description: The project team would like to integrate the holdings of the Family Histories Archive with those of the Church Family History Library catalog.
Status: Hold
Owner: Hold, Unowned Contributors:
Due: TBD Opened: 6/16/2004
Changed: 6/16/2004  
6/16/2004 Identified during the project definition for the first release.
Description: Deliver the search and submission functions in languages other than English.
Projects: Family Histories Archive
Priority: 99 Task ID: 767
Long Description: The project team would like to deliver the search and submission features of the Family Histories Archive in languages other than English.
Status: Hold
Owner: Hold, Unowned Contributors:
Due: TBD Opened: 6/16/2004
Changed: 6/16/2004  
6/16/2004 Identified during the project definition for the first release. This would likely require us to abandon the current code base in favor of a high-end web delivery system that can handle identifying multiple languages. Alternately, we could find out what John Finlay did on phpGedView to delivery additional languanges using open source tools.

Version: 4.0
©BYU 2002, 2003, 2004