• server

Server Design

This is the main organization page for designing and programming the L-Functions Database Server. Currently just a notepad for the programmer Harald Schilly.

Phase 1

• sample data, understand structure, issues, unified structure.
  • later it must be possible to create queries depending on the data, not only the submission itself
  • stored in a directory structure, with subdirectories
• server - waiting for new server
• human readable, easy to understand data description
• separate server and database logic
  • all information and data inside the directories have to be enough to recreate the entire server and database
• [NEW] separate server query and server data representation logic
• submit form for new data
  • enter field and link where to get actual data
  • "admin" configuration to handle submissions
• see progress (functions have parameters, what part of the whole parameter space is covered, what's missing)

Phase 2

• extend query capabilities
• multiple views of the same data (organized by, sorted by, filtered by) x (function, structure, keyword)
  • depends on real world application, need info about that
• access:
  • read free
  • query free (at least for basic operations)
  • registered have more capabilities?
  • no edit (since all submitted data is fixed)
  • replace or delete (if something is wrong)

Interface

Task Flows

Submit New Data, Simple Form

1. form
2. description of data
3. admin reviews (ok/feedback)