{"action":"opened","issue":{"url":"https://api.github.com/repos/KSP-CKAN/NetKAN/issues/1002","labels_url":"https://api.github.com/repos/KSP-CKAN/NetKAN/issues/1002/labels{/name}","comments_url":"https://api.github.com/repos/KSP-CKAN/NetKAN/issues/1002/comments","events_url":"https://api.github.com/repos/KSP-CKAN/NetKAN/issues/1002/events","html_url":"https://github.com/KSP-CKAN/NetKAN/issues/1002","id":70534152,"number":1002,"title":"How do we handle the 1.0 transition for metadata?","user":{"login":"Dazpoet","id":10254092,"avatar_url":"https://avatars.githubusercontent.com/u/10254092?v=3","gravatar_id":"","url":"https://api.github.com/users/Dazpoet","html_url":"https://github.com/Dazpoet","followers_url":"https://api.github.com/users/Dazpoet/followers","following_url":"https://api.github.com/users/Dazpoet/following{/other_user}","gists_url":"https://api.github.com/users/Dazpoet/gists{/gist_id}","starred_url":"https://api.github.com/users/Dazpoet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Dazpoet/subscriptions","organizations_url":"https://api.github.com/users/Dazpoet/orgs","repos_url":"https://api.github.com/users/Dazpoet/repos","events_url":"https://api.github.com/users/Dazpoet/events{/privacy}","received_events_url":"https://api.github.com/users/Dazpoet/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-23T23:01:51Z","updated_at":"2015-04-23T23:01:51Z","closed_at":null,"body":"With KSP 1.0 around the corner it is somewhat important to get a handle on how much metadata updating will be needed in the near future. By knowing which data is affected by manually set `ksp_version` fields we won't have to check through files when someone ask \"why isn't mod X updated to 1.0 in CKAN yet\" since if it's on the list it means it requires some manual changes. I did some filtering to get a list of mods in NetKAN with a hardcoded 0.90 in them. This is the list I got\r\n\r\n```\r\nActsEW.netkan                      \r\nADIOS.netkan                       \r\nAdjustableLandingGear.netkan       \r\nAGExt.netkan                       \r\nAlcubierreStandalone.netkan        \r\nAnimatedDecouplers-x64.netkan      \r\nAnimatedDecouplers-x86.netkan      \r\nAntennaRange.netkan                \r\nAutoAction.netkan                  \r\nBDAnimationModules.netkan          \r\nBetterBuoyancy.netkan              \r\nCommunityResourcePack.netkan       \r\nContractConfigurator-KerbinSpace...\r\nControlLock.netkan                 \r\nCrossFeedEnabler.netkan            \r\nCrowdSourcedScience.netkan         \r\nCustomBiomes.netkan                \r\nDeadlyReentry.netkan               \r\nIFILS.netkan                       \r\nImpact.netkan                      \r\nInfernalRobotics.netkan            \r\nIR-Model-Rework-Core.netkan        \r\nIR-Model-Rework-Expansion.netkan   \r\nKarbonite.netkan                   \r\nKarbonitePlus.netkan               \r\nKerbalFlightData.netkan            \r\nKerbalFlightIndicators.netkan      \r\nKerbalWind.netkan                  \r\nKOSMOS-SSPP.netkan                 \r\nkribubble.netkan                   \r\nkrispeeder1.netkan                 \r\nKSPAPIExtensions.netkan            \r\nMapResourceOverlay.netkan          \r\nMFS.netkan                         \r\nModuleRCSFX.netkan                 \r\nNearFutureElectrical.netkan        \r\nNebulaEVAHandrails.netkan          \r\nOblivionAerospace.netkan           \r\nPilotAssistant.netkan              \r\nProceduralDynamics.netkan          \r\nProceduralFairings.netkan          \r\nRCSBuildAid.netkan                 \r\nRCSLandAid.netkan                  \r\nRealFuels.netkan                   \r\nRegolith.netkan                    \r\nRemoteTech.netkan                  \r\nSDHI-ServiceModuleSystem.netkan    \r\nSmartParts.netkan                  \r\nSmartStage.netkan                  \r\nSnacks.netkan                      \r\nStageRecovery.netkan               \r\nStockBugFixModules.netkan          \r\nStockDragFix.netkan                \r\nStorkDeliverySystem.netkan         \r\nTestFlight.netkan                  \r\nTWR1.netkan                        \r\nUKS.netkan                         \r\nUSI-ART.netkan                     \r\nUSI-EXP.netkan                     \r\nUSI-FTT.netkan                     \r\nUSI-SRV.netkan                     \r\nUSITools.netkan                    \r\nVerticalPropulsionEmporium.netkan  \r\nZeroPointInlineFairings-Lite.netkan\r\nZeroPointInlineFairings.netkan  \r\n```\r\n\r\n65 mods in total and not as many as I thought tbh. These will have to be manually updated and chances are I missed a few. I also realized that e.g. `IR-Model-Rework-Utility.netkan` lacks a `\"ksp_version\"` field and thereby seems to just work on anything (I'm fixing that specific file asap). There might be more files out there that lack `\"ksp_version\"` even though they're not indexed from Kerbalstuff. I'm afraid my filtering-fu isn't strong enough to find these things though.\r\n\r\nIf anyone could run a command in NetKAN that filtered for files not having `ksp_version*` and also not having `#/ckan/kerbalstuff/` that'd be awesome so their metadata can be updated prior to 1.0.\r\n\r\nI also filtered for files having `ksp_version_min` and that list was rather short I made a PR which adds corresponding `ksp_version_max` fields to them. Not sure if this is the right call or not?\r\n\r\nCKAN-meta is a whole other story... Maybe a list could be made from filtering files that don't include `\"x_generated_by\": \"netkan\"` ? I expect CKAN-meta to be a lot more hellish to deal with but I think (hope) that most core mods are in NetKAN, save of course for stuff like all the Kopernicus and planetbuilding stuff which is a whole story in itself."}}