uwdub/web-dub

web-dub's Issues

Test AuthorID format

Define as id_(lastname)_(firstname), all lower case, any spaces replaced with underscore.

This is implemented as the first two fields.

Provide an explicit override option.

Decide on Faculty Affiliations/Listings

Faculty can have affiliations in multiple departments, some have many more than others. For the sake of organization..

• Should we include affiliate departments?
• Should we put a cap on how many to list?

This is related to #99.

Publications: Test for Orphaned Files

When we get back to working on publications:

Add test that confirmed all publication files are referenced. We currently have some orphaned PDFs.

Calendar - Add Older Seminars

In part because it makes the videos more accessible.

Fix Faculty Titles / Affiliations / Websites

I have imported faculty from the old DUB website. That old website did not include titles, and also includes incorrect information regarding many affiliations and websites. So the imported faculty need to be checked and fixed. Note we are not creating new faculty. Our goal is to have some faculty correct, such that when we go public it is clear what information additional faculty need to include in a profile. We will have a similar process when I import the students.

There is a _people/faculty directory. People in this publish when the site is generated.

There is a _people/faculty/_unchecked directory. These people need to be checked still.

There is an _people/alumni/faculty directory. These people are no longer active in DUB. This directory does not publish when the site is generated (because of the leading underscore). We are keeping these files around so that we can be organized when we decide what to do with alumni, but there are no plans for them prior to launch.

I have already moved inactive faculty to _people/alumni/faculty.

For each faculty file in _people/faculty/_unchecked, we need to:

• Check the correctness of name, position , web, twitter.
  This requires a search for the faculty member's primary website and updating these fields.
• Move the resulting file to _people/faculty.

When you check / fix a faculty member, submit a pull request referencing this issue.

Removing pubnum should be a test

Now that our data does not include any pubnums, we don't need a script to remove them.

Instead, convert that to a test that will confirm no publications have pubnums.

Assign People to Roles instead of Tags

Based on #63, faculty / student status is a role and not a tag.

Link Color Not Visible

The purple I've been using makes links basically impossible to see.

We need a new color.

Static Content: Mailing Lists

We need next regarding the mailing lists and how to sign up. See this page on the old site:

http://dub.washington.edu/mailinglist

Our current lists are:

• dub
• dub-faculty
• dub-students
• dub-social

These are special purpose lists:

• speak
• dub-exec
• mhcid-exec
• dub-web

If we can create a basic page for this, the text will be available as we start to develop page templates and organize other static content.

Cleaning TBD Titles on Upcoming Talks

A common scenario is that we have a speaker scheduled, but no title yet. Currently, this just appears as TBD in several places (the front page, the calendar). Let's instead emphasize the speaker.

This starts in part from an @andyjko observation:

On the calendar, there are many entries with "TBD" headers that nevertheless have names next to them. After digging around, I figured out that "TBD" is the title of the talk. I think it would be less confusing if we just skipped the title altogether if it's empty.

I think it requires:

• Updating the main page to show speaker name (i.e., always).
• Updating the main page to not show TBD titles.
• Updating the calendar page to not show TBD titles.
• This may require changing our TBD syntax, having a few field-specific flags instead of one global.

Clean up and document tests

Journal ID and Journal Paper ID Standarization

Same basic procedure as conferences.

Google Snippets

Ensure Google generates appropriate snippets for the main page.

For the old page, I was spuriously identified as a snippet:

Two-Column Format for People

Figuring out Jekyll tags for a two-column format for people.

Add People Tests

We are starting to make requirements regarding the data associated with people.

We should enumerate those and define tests that correspond to them.

Sidebar: Getting Involved

Create a sidebar to navigate the different sections of 'Getting Involved'.

(Alternatively, we also considered using accordions to organize this page.)

DUB Mailman

http://dub.washington.edu/mailman/listinfo/dub

Start with New Template

Let's start with this being fairly lean. Use this as a simple template:

http://pixelarity.com/standout

Import Alumni from Old Website

We are not doing anything with alumni right now, but have some alumni as part of importing and cleaning up the existing student data. Import the alumni from the old website so that we have it all together.

Add People

This is an old issue, which we'll want to unpack when we really get started on adding people.

We need to populate our people. This is a big task that will need broken into lots of steps.

• #59 Fix Faculty Titles / Affiliations / Websites
• #62 Decide How to Group Graduate Students
• #63 Decide How to Title Graduate Students
• #64 Import Graduate Students from Old Website
• #65 Fix Graduate Student Titles / Affiliations / Websites
• #66 Import Alumni from Old Website
• Decide How to Handle Affiliate Faculty / Postdocs / Research Collaborators

After we have "enough people" posted, we can go public and get more DUB people to add themselves (or at least surface so that web-dub can submit the pull request on their behalf). So we will define "enough people" as importing the existing DUB website and cleaning it up a little.

Avoid breaking URLs when possible

The current dub site is pretty well indexed -- both normal Google and Google scholar, with some dub folks using it as their primary profile or primary papers repository and many PDFs hard-linked from other sites around the web.

If the URL schema changes, we (you?) ideally could 301 Redirect for at least author pages, paper PDFs, and paper pages. (possibly project pages too?)

People - Normalizing Thumbnail Photos

Find a way to easily generate thumbnails for the People page. This could be done manually in Photoshop, but we are looking for a method that is more easily transferable for maintenance purposes.

Features:

• Circular border (this can be done in Bootstrap)
• Square dimensions (100x100)
• Centered on the face
• Greyscale

Part of #99

Conference Paper ID Standardization

Propose a standard for naming conference paper id.

I think it's probably:

id_conferencepaper_{}_{}

Where the first field is the conference id, with the id_conference prefix removed:

chi2011

The second field is the the id of the first author, with the id_author prefix removed:

patel_shwetak

If that ID is unique, it is sufficient. If the same author has more than one paper at a single conference, a further identified will be needed:

id_conference_{}_{}_{}

The third field can be any word, used as a unique slug. For papers which need a third, add a field:

 id_slug: hydrosense

Write a test that checks all paper ID follow the above formats.

Write a test that checks all paper ID are unique.

Get existing data consistent with the format.

Misnamed Class

In test_authors.py, the class should be TestAuthors instead of TestConferencePapers

Use safe_load and safe_dump throughout

Conference ID Standardization

Propose a standard for naming conference id.

I think it's probably: id_conference_{}

Where that field is probably shortname, with spaces removed, converted to lowercase.

It will sometimes be: id_conference_{}_{}

With some "track" appended (e.g., see aaai2008_nectar versus aaai2008_seniorpapers).

Write a test that checks this format.

Get existing data consistent with the format.

Decide Regarding dub-studies Mailing List

The DUB list is being used to advertise studies, which detracts from the value density of the list.

When we publish the lists, we should be clear on this. Perhaps also create a studies list so people can opt-in to these types of emails.

Calendar - Create iCal and Subscribe Links

We'll want to use the same data that's driving everything else to create an ICS file.

Then we'll want to publish that link, and give people the ability to subscribe.

The Google subscribe link seems to be:

https://calendar.google.com/calendar/render?cid={{ http_path_to_ics_file }}

It also seems like maybe this is a thing:

webcal://{{ path_to_ics_file }}

Workshop and Workshop Paper ID Standardization

Same basic procedure as conferences.

Main Page - Iterate on Carousel Items and Text

Let's try five things:

• Design
• Use
• Build
• Research
• Education

Iterate on the text underneath. Use viable images for now, we'll finalize the images for launch.

Wireframe People

Figure out how we want to profiles to look.

To do so, we also need to figure out what we want on each person's 'profile' page.

These are what I propose:

• Name
• Role + Position (title + unit)
• Picture
• Email
• Office
• Website

We want these pages to be as static as possible without having to constantly update or badger people to update, so do we want to bother with a short blurb?

Add Publications

As described in the README, we will launch without publications.

A publications branch does exist where we will eventually work on importing publications.

But getting launched is the priority.

Publication Files Should Be Named by ID

Instead of this:

id_conferencepaper_pervasive2010_welbourne_evan:
  authors:
  - id_author_welbourne_evan
  - id_author_balazinska_magdalena
  - id_author_borriello_gaetano
  - id_author_fogarty_james
  conference: id_conference_pervasive2010
  localpdf: pervasive2010.pdf
  localthumb: pervasive2010.png
  officialurl: http://dx.doi.org/10.1007/978-3-642-12654-3_4
  pages: 57-75
  title: Specification and Verification of Complex Location Events with Panoramic

We should have this:

id_conferencepaper_pervasive2010_welbourne_evan:
  authors:
  - id_author_welbourne_evan
  - id_author_balazinska_magdalena
  - id_author_borriello_gaetano
  - id_author_fogarty_james
  conference: id_conference_pervasive2010
  localpdf: pervasive2010_welbourne_evan.pdf
  localthumb: pervasive2010_welbourne_evan.png
  officialurl: http://dx.doi.org/10.1007/978-3-642-12654-3_4
  pages: 57-75
  title: Specification and Verification of Complex Location Events with Panoramic

Note the different localpdf and localthumb.

Similarly for other publication fields and types.

Reorganize Seminars

The idea is to replace the Google Calendar with our own file structure and look.

• Create preliminary seminar files (files for Winter 2015 were added #106)
• Create sidebar layout for Current/Previous Seminars. Previous Seminars will be a separate page.
• Create a filter that determines if a seminar file is current or previous.
• Current/Previous seminar pages will include: name, affiliation, title, date, time, and location.
• Seminar sub-pages will also include: abstract, bio, video (optional)
• Display info on the next upcoming seminar, and a link to the calendar page on the Front page.
• Create seminar files for all previous seminars from the Google Calendar (finish migration)
• Filter Previous Seminars by year, and have the sidebar automatically update. Implement pagination.
• Some seminar file entries may be incomplete (a placeholder with name and date, but no title). Figure out some system to include 'TBD' placeholders when fields are incomplete.

Adding new seminar content:

• The people in charge of creating/updating new seminar information will need to submit a pull request. Initially provide a template. Eventually we may create a form to make submission easier.
• Find some way to deal with the issue of 'smart quotes'.

Post-seminar content:

• Create a video field in the seminar file. Include the video embed on the seminar page if available. TODO: make embed responsive to small screen size
• Contact the person in charge of uploading the video (currently the MHCID Web Coordinator). They will be in charge of additionally adding the Vimeo video id to the seminar file.

Create basic seminar content

Create some basic content for the DUB seminar, so that we can style it

Add LESS Support for Styling

I'm working on this in the base.

Implement People

For the internal launch, we are going with:

• Round-frame black-and-white photo
• Name (hyperlink to personal site)
• Department(s)

Eventually there will be sub-pages with additional info such as:

• A short blurb (maybe - but this may need maintenance so maybe not)
• Publications

Static Content: About DUB

Currently this page contains:

• Several paragraphs talking about DUB and its history.

Also (will commit this soon):

• A listing of all the involved DUB units.
• Previously there was graduate program info on this page. This will be moved to 'Getting Involved'.

@jayfo I believe you mentioned adding information on the DUB structure (leadership and units). Is this information still being finalized, or is it available?

Finalize Carousel Pictures for Launch

Decide How to Announce Various Events/News

Currently, the calendar page just contains a listing of upcoming seminars.

• Do we even want to add other types of events to the calendar page?
• If so, how do we want to organize this? Create a separate collection?

Style website

The site still looks like the template we started with. It needs some purple, and some design love.

[ ] #75 Two-Column Format for People

Create a Calendar Page

This will be a page that will contain the calendar of DUB events, which may eventually include:

• weekly seminars (including details, and maybe a link/embed to the vimeo stream. does this need its own subsection?)
• other dub events (e.g. retreat)
• other items of interest from participating units?

For the moment I am embedding the existing Google Calendar into the page, but once we get seminar/event data more organized we should figure out how to organize the page.

Note: there will also be a small dub seminar calendar module on the front page so people can easily access that information from a glance.

Update README to set basic development goals

Fix Graduate Student Titles / Affiliations / Websites

After we decide how to title graduate students, we need to check the imported graduate students.

So this is waiting on #63.

Decide How to Group Graduate Students

@jayfo said:

It has come up that a single category of "graduate students" might not be right. We have a bunch of PhD students, and we have a bunch of Masters students. What should the heading be above everything?

Option 1:
Graduate Students

Option 2:
PhD Students
Masters Students

What you think? Any other option I'm missing?

@andyjko said:

I think it makes sense to split them. PhD students are here for so much longer and they do very different things from masters students on campus.

@jayfo said:

And with a landslide vote, it was decided.

Import Graduate Students from Old Website

Import the graduate students from the old website.

Decide How to Title Graduate Students

Faculty can have one or more position, each of which consists of a title and a unit.

position:
- title: Associate Professor
  unit: Information School
- title: Adjunct Associate Professor
  unit: Computer Science & Engineering

It seems clear students have one or more unit. But what about title?

We already decided to group students as "PhD Students" and "Masters Students" (see #62). We could eventually find that we want or need an "Undergraduate Students".

Given that, what is an appropriate title? Or should there be no title? Remember we have several different units and types of student to consider, and we want a consistent approach.

position:
- title: PhD Student
  unit: Information School

position:
- title: Masters Student
  unit: Human Centered Design & Engineering

position:
- title: Masters Student
  unit: Division of Design

position:
- title: Masters Student
  unit: Human Computer Interaction & Design

position:
- title: Undergraduate
  unit: Information School
- title: Undergraduate
  unit: Computer Science & Engineering

The most prominent display of these will be on the people pages.

Note that the above splits the M from MHCID. Another potential example of a title I am missing here is something like Undergraduate Researcher. So I do not think the above are perfect, I am just using them to illustrate some of the range.

What do we think? Are they right? Better ideas? Something we're missing?

@andyjko, @depstein, @mjskay

Static Content: DUB Logos

We should preserve the DUB logo content available here:

http://dub.washington.edu/logo/

This issue is focused on preserving those logos, not updating or changing them. That could happen later, but is not part of the current discussion.

I have created a simple directory and stub file that could be edited for this content:

https://github.com/uwdub/web-dub/tree/master/logos

https://github.com/uwdub/web-dub/edit/master/logos/index.md

Static Content: Getting Involved

Create content for 'Getting Involved'

This content is split up into sections:

• Mailing List (there is also a separate 'Mailing List' page with the same info)
• Seminar (this is brief blurb that has a link to the 'Calendar' page)
• Current Students, Researchers and Faculty
• Prospective Students (Admissions?)

Thoughts on these sections and their titles?

Other people to consider:

• Undergrads
• Industry Sponsors

We also need to decide on who to be the point of contact for people interested in DUB.

Write Tests that IDs are Unique

There should be a test that IDs are unique. We need one in:

Authors
ConferencePapers
Conferences
JournalPapers
Journals
WorkshopPapers
Workshops