Weekly Meeting:

What's been happening?

  • Beth: do we want to alternate between dev-only and dev/management meetings?
  • "Rick's webpages": Marlon is moving link of webpages from dev. hadn't realized Rick was using it live.
    • Rick's requests for "Affiliations" section. inside/outside university. still defining terms. Call it Designations; Marlon will follow up with Rick.
  • Ray handling various watiam issues/questions (unspecified)
  • Marlon: Noki's code for building specific administrative report: where should we put it?
    • Beth: how generic is this tool? It runs an SQL query. It will be useful for Engr Dean's Office...
      • And also possibly for CS- Marlon/Beth say we should pay attention to this section when it is part of the trunk code.
  • Daniel: discussions we've had with Peter Forsyth on usefulness of different reports; he's excited about automating Accreditation reporting, which we'd not previously mentioned to him. Also, excited about outputting grad-supervision data/publications/courses-taught on his webpage- discussed server-side includes to make that easy for him to include in his existing page.
  • Tamir: overall what reports can be generated?

Reports Currently output for Engineering

  1. Merit
  2. CV
  3. accredation report for professor
  4. OCGS report section on CVs
  5. NSERC (longer-term future).

Two additional kinds of reports have been added:

  1. statistics on data, for admins (Engr Dean's Office)
  2. webpages (enhanced from basic version: see above, "Rick")
  • OCGS report data is compete for all faculties.
    • data from Rch office, Grad studies office. BUT missing data for "lifetime record of publications" (& 6 year summary) which profs must add to OFIS.

Discussion of Bibtex continued to:

Overall directions?

Beth will write up and email the list.

Overall timing suggestion: October, for CS to have tools for the profs to try out.

BibTeX

  • handling our problem differentiating contribution types upon input: We can dump un-identified items into "General sort"
    • their list of contribution types "needs cleanup".
      • some are specific to Engineering. Some are probably missing, as needed in CS.
    • Overall, Contributions section needs cleanup. It's a major section of the site.
  • How to upload bibtex data?
    1. text field on webpage
    2. upload field on webpage: to upload file from browser
    3. input field on webpage: URL to grab file directly
    4. input field on webpage: URL, grab all .bib files on that page.
    5. finally: all of the above?
    • Some profs don't use bibtex, just latex. How to handle? Can we try for assuming a common order to data?
      • Maybe. Doubtful. But we can try it anyway. Beth would like to see that.

Reports

  • CS will want to see RTF and LaTex output, at least; probably html as well.

HTML output

  • Marlon plans to steal Rick's templates.
  • discussion of how to get from prof's page to faculty's page... between Marlon/Ray/Beth.
  • HTML including Research and Students useful to CS.
  • to be determined later: dynamic or static output

Overall interface cleanup

  • (Contribution type- one part of it)
  • import via text-fields on webpage?
    • or single field?
    • or spreadsheet?
  • ajax to manage preserving data? merge view/add screens?
  • Tamir suggests a particular format: text-entry at top, with list of current views below, in reverse chronological format
  • Work on contribution-type cleanup: can be Jack or Tamir. Decide between them.

Reports

  • Tamir will work on cleaning up RTF templates. In CS first, and offered to also do Engr once he understands the formatting.
  • what's the most essential? Marlon would like to see us output a CS report; though Peter F. suggests profs won't find it interesting.

Upcoming technical meetnigs:

  • Daniel will present on svn merging
  • Tamir will present on PDO and sql.

Completed Tasks

  • Tamir: investigation into Reports coding -> many questions
  • Daniel: looked into svn via file://
  • Daniel: make some sort of comment to the group about reporting code and whether it's reasonable to take on the task of OFIS report modifications (as part of output development). - sort of solved: we're going to be handling a batch of these.

Upcoming Tasks

  • Tamir/Dawn: self-signed certificate
  • Daniel: continue learning about svn branches and merging, to give a demo.
  • Daniel: get information from current OFIS users
  • [...]

-- DanielAllen - 09 Sep 2009

Topic revision: r2 - 2010-05-05 - DanielAllen
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback