Jump to content

Arrakus

Members
  • Content Count

    406
  • Joined

  • Last visited

About Arrakus

  • Rank
    Member
  • Birthday

Recent Profile Visitors

524 profile views
  1. Thanks Oggdude. I GREATLY appreciate the help! Will let you know how it works.
  2. That is probably because I am doing a piss poor job of explaining it. Issue: The program will not import a data set if the first folder in the compressed file does not read "Dataset_(NAME)". If the first folder is not named "Dataset_(NAME)", then the program gives the following error: “This ZIP archive does not contain a valid Data Set” Occurrence: When compressing a data set by a program other than Data Editor, it is possible that the naming definition for the first folder in the compressed file will not read "Dataset_(NAME)". But instead will read “SWData*”. This will cause an error and the data set will not be able to be imported. Work Around: Manually rename the first folder in the compression file to "Dataset_(NAME)". Possible solution: Change the naming convention for the first folder in data set to match the naming convention for the compressed file, for example to “SWData*” Additional info: This naming requirement is not explained in the FAQ (Neither of them are). Making it difficult to figure out what the problem is and how to fix it.
  3. The dataset is at a hosted location, unzipped. Encountered the issue when downloading the dataset, compressed via ZIP and then attempting to import it. That is when we noticed file name format specifics. Unfortunately changing how the hosted location names the first folder inside the ZIP compression is challenging, at best. Is it possible to loosen or change those file name definitions? From "Dataset_<data set name>" to "Dataset*" Admittedly I am not a program; have no idea how plausible that maybe.
  4. Hey Oggdude, Was this below able to make it in to the patch? I did not see information relating to it in the notes. Would be helpful if it could. Thank you!
  5. I created an account over at Gitlab and have been maintaining a current data set (as current as one can be) over there. It has been up for about 3-4 months now, Link: https://gitlab.com/rikus01/SWDataSet-OggDudes Which would you rather do, the Google Groups that you have set up or this? I do not mind working with Gitlab project to keep it current.
  6. Hey Oggdude, This may be on of the more weird requests. Currently when importing a new data set, the compressed data set and the first folder inside the data set have to follow a specific naming convention. For example; the compressed file has to be named "SWDataSet-(*****)". While the first folder inside the data set also has to be named "Dataset_(*****)". The difference in the two naming conventions has caused some problems when sharing data sets between users. The naming convention for the compressed file is not an issue. However the naming convention for the first folder inside the data set is. Is it possible to either remove the naming convention restriction for the first folder inside the data set or make it so it matches the naming convention for the compressed data set. For example, both the file and folder have to be "SWDataSet-(*****)". Lastly, we have noticed we are unable to import data sets if that data set was compressed by Win10. However, if the data set was compressed with *.tar or *.rar, there are no issues. Not sure why that is.
×