today

[Jason Priem]

Did: 

"download data" button gets csv. Each item gets a row, and each metric is a column...I think this is easier to read and work with than the "molten" format the current app serves, with each value getting its own row. 

Tomorrow:

Rows are currently keyed just by tiid; we need other unique identifiers per row if we want this to be useful. I'm thinking another column called "identifier," which is populated with the best id (for simplicity, just go doi->pmid->url, since github, slideshare et al. ids are encoded in the url). Should be a fairly quick job.

Will fix on fix frontpage links and add logos

Will populate about page with static_meta descriptions from providers.

With luck, will finish these in time to start looking at speeding up the initial creation of items.

Potential obstacles:

General slowness and CPU-intensiveness of application continues to annoy; difficult to not dive in to logs and figure that out. Shall wait, though, till Heather gets her profiling results (tomorrow?), as that will be very informative.

--
Jason Priem
UNC Royster Scholar
School of Information and Library Science
University of North Carolina at Chapel Hill

[Kevin Campbell]

On Thu, May 24, 2012 at 7:27 AM, Jason Priem <j...@jasonpriem.org> wrote:

Did: 

"download data" button gets csv. Each item gets a row, and each metric is a column...I think this is easier to read and work with than the "molten" format the current app serves, with each value getting its own row. 

Tomorrow:

Rows are currently keyed just by tiid; we need other unique identifiers per row if we want this to be useful. I'm thinking another column called "identifier," which is populated with the best id (for simplicity, just go doi->pmid->url, since github, slideshare et al. ids are encoded in the url). Should be a fairly quick job.

Will fix on fix frontpage links and add logos

Will populate about page with static_meta descriptions from providers.

With luck, will finish these in time to start looking at speeding up the initial creation of items.

Potential obstacles:

General slowness and CPU-intensiveness of application continues to annoy; difficult to not dive in to logs and figure that out. Shall wait, though, till Heather gets her profiling results (tomorrow?), as that will be very informative.

Jason,

If the issue is that we're doing multiple requests per item, that should be very obvious from the logs. Feel free to start with a clean instance (remove all logs), take a note of your actions, and then tar up and send over a copy of those logs for me to have a check.

Regards,
Kevin

[Jason Priem]

Thanks Kevin. Headed to bed right now, but will send you that in the morning.

J

Sent from my iPad

--
You received this message because you are subscribed to the Google Groups "total-impact-dev" group.
To post to this group, send email to total-im...@googlegroups.com.
To unsubscribe from this group, send email to total-impact-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/total-impact-dev?hl=en.