joebillings
commented
5 years ago The htaccess is failing on this pattern. As discussed with CM, we've decided to only include a date where necessary and include it in the project name. Here is the discussion from Signal:
Joe: We need to have an sandbox/staging area for lod and a final release one so that we don't break things when working on changes. I was trying to have a catchall rule in the htaccess for the sea-lod (oxford and newbridge) that could also be used in dotcoop but I don't think it's going to be possible. Will need to have an element of hard coding n there or rethink URIs
The current pattern is to have {domain}/project/year/{files} for final and {domain}/project/{files} for pilot but there's no way to catch both of those using a generic regex in the htaccess
I think the best option would be to change the patterns so they're both the same: {domain}/project/year/{files} and {domain}/project/sandbox/{files}
Colm: I think the year is from co-ops uk data, before they shifted to quarterly publishing?
Joe: When we spoke with Matt at Tap he said that it was good practice to include the date in the URI. I can't really see a huge benefit to it myself unless we're going to create a new one each time we publish the data. Happy to just do {domain}/project-pilot/{files} and {domain}/project/{files}. It would make things easier.
Re "create a new one each time we publish the data" - the benefit would be a way to look back through the data. Not sure of practicalities for large sets
Colm: I think there are two different use cases.
1) When we only want to maintain on data set and keep it up to date.
2) When there are periodic updates, where the history is valuable.
Given that right now only Co-ops UK is type 2, we could put the date in the project name?
Currently the Oxford data is sitting in an experimental location (w3id2.solidarityeconomy.coop/sea-lod/oxford-pilot/). This should be moved to a final location (w3.org/sea-lod/oxford/yyyy-mm-dd/) so we can continue to experiment without breaking the live site.