Freshmeat becomes Freecode, and how our data is affected
Three things happened recently to affect our Freshmeat collection
1. Freshmeat announced a name change to Freecode.
2. We have an issue (issue #43) that talks about how the trove definitions for Freshmeat are out of date.
3. Freshmeat replaced trove with tagging and we missed the memo
What I've done is as follows:
For issue #1 - decided not to rename our abbreviation for Freshmeat. It will remain "FM".
For issue #2 & 3 - Added a new table to hold the tags associated with a project. It's called fm_projects_tags.
CREATE TABLE IF NOT EXISTS `fm_project_tags` (
`project_id` int(11) NOT NULL DEFAULT '0',
`datasource_id` int(11) NOT NULL DEFAULT '0',
`tag_name` varchar(50) NOT NULL DEFAULT '0',
`timestamp` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
PRIMARY KEY (`project_id`,`datasource_id`,`tag_name`),
KEY `datasource_id_index18` (`datasource_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
Added a new release file to hold the data from this table. The new file is called fmProjectTags2011-Nov.txt. Did not remove trove; we are still collecting the trove. Although there is no longer any "trove definition" list that I know of to describe each trove number, so these are not as useful as the "tags". But I'm leaving this alone in the database for historical purposes.
Here is a shot of the tags page for a sample project on Freshmeat, called amms.
Here is a shot of the way the tags look now in our release files (or database table) for that same project (#78922)
Attachment | Size |
---|---|
Screen shot 2011-11-17 at 11.50.04 AM.png | 10.67 KB |
Screen shot 2011-11-17 at 11.50.15 AM.png | 24.26 KB |
- megan's blog
- Log in to post comments