Ticket #990 (assigned)

I don't think there is a log view in Studio (yet). The log is a table in the database called "playLog", created by this command: CREATE TABLE playLog ( id BIGINT NOT NULL, audioClipId BIGINT NOT NULL, timestamp TIMESTAMP NOT NULL, PRIMARY KEY(id) ); Currently, we only log audio clips (i.e., for a playlist played, we do not log the playlist's ID, only the IDs of the audio clips inside it).

Whats now?

I'd say this is a version 1.1 feature request. We need Doug to agree, though...

So will we have at least a text file that the system outputs? If it's only a database table, someone will need to document how it works, what it captures, and how to use it. 1.0 has to have at least _some_ kind of log function. It may not have to be in a window in the browser, but it has to be there. Based on the feedback I'm getting, log functions are crucial to whether a station keeps its license.

It's pretty easy to get a text file from the database: $ pg_dump -t playlog -a livesupport > playlog_dump.txt will produce something like this: >>> playlog_dump.txt file begins >>> -- -- PostgreSQL database dump -- SET SESSION AUTHORIZATION 'test'; SET search_path = public, pg_catalog; -- -- Data for TOC entry 1 (OID 585316) -- Name: playlog; Type: TABLE DATA; Schema: public; Owner: test -- COPY playlog (id, audioclipid, "timestamp") FROM stdin; 1 10001 2005-02-24 15:11:02 2 10005 2005-02-24 15:13:29 3 10001 2005-02-24 15:15:40 \. <<< playlog_dump.txt file ends <<< It's probably not very hard to combine this with some batch psql commands in a script to produce a similar list, but with title and creator (and copyright holder, if filled out) instead of the unique ID.

this is related to #505* , which would be the information gathering part, while this is the UI part of the same feature.