Create "Settings" screen to edit document types and people roles
Add field to People Detail (person table) for ancestry.com, familysearch.org, etc IDs. (Leverage existing data)
Add ability to renumber/reorder pages. (What happens when they get imported out of order?)
Consider adding link to location/place fields to Google Maps
Host app through Cloudflare (like HA) after upgrading db to postgres
Investigate open source, locally hosted, purpose-built LLM
Investigate how separate form text from filled in data, and how to treat it.
Investigate API link to FamilySearch.org to populate date-driven data, like census records, birth & marriage records, etc. This might help establish location context for letters.
Add ability to create a document transcription in markdown format (including thumbnails of each page?)
Add ability to upload additional profile pictures and homepage images.
Add pan & zoom wrapper to Source Detail image (This is not necessary for the Homepage or Document Detail page.)
Load the images in a viewer with left/right navigation arrows that allow you to toggle through the images
Add a description field for the images that displays below the current photo.
Home page image viewer should be a slide show
Consider using a washed out (30% opaque) version of the homepage image as the background wallpaper on all other screens
Remove "Saved ..." from upper right corner of menu bar. It doesn't do anything.
Add ability to create "collections" of documents. (Examples: Eugenics-related, Hig's postcards to Zenna, John E Cochran books.) Adding tags may solve the problem better. (Examples: Lancaster + Eugenics, Higgins + Hig's postcards to Zenna...)
Upgrade to postgresSQL, docker + Cloudflare remote access
Add User logins with different access levels (RO, ability to edit transcriptions, ability to upload new documents, etc)
Flatten v4 documentation
Upgrade/update .github skills/instructions
* ~~Create "Settings" screen to edit document types and people roles~~
* ~~Add field to People Detail (person table) for ancestry.com, familysearch.org, etc IDs. (Leverage existing data)~~
* Add ability to renumber/reorder pages. (What happens when they get imported out of order?)
* Consider adding link to location/place fields to Google Maps
* Host app through Cloudflare (like HA) after upgrading db to postgres
* Investigate open source, locally hosted, purpose-built LLM
* ~~Investigate how separate form text from filled in data, and how to treat it.~~
* ~~Investigate API link to FamilySearch.org to populate date-driven data, like census records, birth & marriage records, etc. This might help establish location context for letters.~~
* ~~Add ability to create a document transcription in markdown format (including thumbnails of each page?)~~
* Add ability to upload additional profile pictures and homepage images.
* Add pan & zoom wrapper to Source Detail image (This is not necessary for the Homepage or Document Detail page.)
* Load the images in a viewer with left/right navigation arrows that allow you to toggle through the images
* Add a description field for the images that displays below the current photo.
* Home page image viewer should be a slide show
* Consider using a washed out (30% opaque) version of the homepage image as the background wallpaper on all other screens
* Remove "Saved ..." from upper right corner of menu bar. It doesn't do anything.
* Add ability to create "collections" of documents. (Examples: Eugenics-related, Hig's postcards to Zenna, John E Cochran books.) Adding tags may solve the problem better. (Examples: Lancaster + Eugenics, Higgins + Hig's postcards to Zenna...)
* Upgrade to postgresSQL, docker + Cloudflare remote access
* Add User logins with different access levels (RO, ability to edit transcriptions, ability to upload new documents, etc)
* Flatten v4 documentation
* Upgrade/update .github skills/instructions
API link to FamilySearch.org not available to me for a variety of reasons:
Solutions most likely to be REJECTED include:
Read-only without creating meaningful new content for FamilySearch or its contributors
Makes it difficult to service FamilySearch users and third-party solutions. Personal, individual, or student academic projects.
Submitted in languages other than English Open-source tools without a business marketing model of executable code Prototype or proof-of-concept projects
Extensions deliverable as only browser plug-ins
Use AI to generate information uploaded to FamilySearch without full disclosure and approval by FamilySearch
If your project matches one or more of the above REJECTED items, PLEASE DO NOT SUBMIT!
API link to FamilySearch.org not available to me for a variety of reasons:
Solutions most likely to be REJECTED include:
Read-only without creating meaningful new content for FamilySearch or its contributors
Makes it difficult to service FamilySearch users and third-party solutions.
**_Personal, individual, or student academic projects._**
Submitted in languages other than English
**_Open-source tools without a business marketing model of executable code_**
**_Prototype or proof-of-concept projects_**
Extensions deliverable as only browser plug-ins
Use AI to generate information uploaded to FamilySearch without full disclosure and approval by FamilySearch
If your project matches one or more of the above REJECTED items, PLEASE DO NOT SUBMIT!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Create "Settings" screen to edit document types and people rolesAdd field to People Detail (person table) for ancestry.com, familysearch.org, etc IDs. (Leverage existing data)Investigate how separate form text from filled in data, and how to treat it.Investigate API link to FamilySearch.org to populate date-driven data, like census records, birth & marriage records, etc. This might help establish location context for letters.Add ability to create a document transcription in markdown format (including thumbnails of each page?)Identifying form text and filled in data added in v4.2
Added document printing in V4.4
Add Settings page in V4.3
API link to FamilySearch.org not available to me for a variety of reasons:
Solutions most likely to be REJECTED include:
Read-only without creating meaningful new content for FamilySearch or its contributors
Makes it difficult to service FamilySearch users and third-party solutions.
Personal, individual, or student academic projects.
Submitted in languages other than English
Open-source tools without a business marketing model of executable code
Prototype or proof-of-concept projects
Extensions deliverable as only browser plug-ins
Use AI to generate information uploaded to FamilySearch without full disclosure and approval by FamilySearch
If your project matches one or more of the above REJECTED items, PLEASE DO NOT SUBMIT!