Disappointed With Recent Changes to WixData

Hi Noah,

Thanks for sharing the link regarding Custom Quotas. What is the actual process for requesting a custom quota? The “Contact our Sales Team” link in the wix article you posted offers two options: (1) Contact Customer Care or (2) Talk to an Enterprise Expert. Because I don’t want to move up to Enterprise but instead want to add a Custom Quota to a Wix Studio Elite plan, I chose Customer Care.

Unfortunately, Customer Care’s eventual answer to “I’d like to add a custom quota to an Elite plan. How do I do that?” was to direct me to my site dashboard to “upgrade my plan.” Ultimately, Elite is the highest option available, so HOW do we go about requesting a custom quota? Do we need to work directly with the Enterprise team even though we don’t want Enterprise?

Thanks!

@noahlovell Hello again, Noah. Any additional info on the process for requesting a custom quota? (see my post above for more detail)

Thanks!

Hey!

Sorry, was OOO - arrived back today and just seeing this now :slight_smile:

If you contact Enterprise, you won’t be made to move to an Enterprise plan, it’s more since they’re the team that handles custom quotas it gives them an opportunity to see what you need and to talk through the Enterprise option should you need it.

Are you able to send me a message with the ticket number from Customer Care if you have it to hand?

1 Like

Gotcha! It was an customer care chat so I didn’t get a ticket number.

I’ll contact Enterprise directly to figure out next steps. Thanks!

Hello. @noahlovell I have become aware of the cap on CMS a few days ago and have read through the threads posted here. I have started a Wix website containing databases of registers of enslaved peoples at the Cape Colony in South Africa from 1652 to 1900. The publication of the registers will help thousands to trace their ancestry. We have a complex society, built on slavery which led to Apartheid and many are oblivious to our origins. My website is a free use website. I am a pensioner and a descendant of those slaves, and I cannot afford one of the higher Wix plans because of the exchange rate between the USD and ZAR. Loading the data is painstaking and time consuming as I have to read through archives that are hundreds of years old. The 10 000 cap on the Core plan will make it impossible for me to build further on the records which I have already loaded. I am not a developer or coder and the Wix platform is ideal for loading my databases. I hope someone can advise me on a course of action to follow.

Hi, Batya_Cornelius !!

Hello, You’re doing amazing work. I believe that, with a simple database like the one you’re building, where past data is manually entered for visitors to view, it should be possible to operate beyond the item limit by storing data accordingly. The item limit set by Wix is, I assume, a limit on the number of records, so if you save structured text data, such as JSON, within a single record, it should be feasible to store more than 10,000 entries.

However, this method might require some clever approaches when it comes to searching within that data. If your main constraint is financial, then this approach could be a reasonable solution. :wink:

1 Like

Hi @onemoretime . Thank you for your response and encouragement. I am building the databases in Wix CMS table and using the Wix filter system for searches of specific fields in the table. The databases are therefore like an Excel spreadsheet with several searchable fields for the uploaded data. As I mentioned previously, I am not a coder and am using Wix available elements for my website. I do not know what JSON is or how to use it.

Hi, Batya_Cornelius !!

Think of JSON as a way to store structured data in a text format. Instead of saving data for one person in a single row of your database, you can define a text field in your database row and write data in JSON format there, allowing you to store multiple pieces of data in a single row.

With the help of ChatGPT, here’s an example of what JSON data looks like:

{
  "library": [
    {
      "title": "The Great Journey",
      "author": "F. Scott Fitzgerald",
      "yearPublished": 1925,
      "genre": "Adventure"
    },
    {
      "title": "A Quiet Place",
      "author": "Harper Lee",
      "yearPublished": 1960,
      "genre": "Fiction"
    },
    {
      "title": "Bright Future",
      "author": "George Orwell",
      "yearPublished": 1949,
      "genre": "Philosophical"
    }
  ]
}

You would input this JSON data into a text field in your database. Then, if you were to retrieve this data from the database (where you would likely need to perform a text matching search on this field), you could apply filtering in your JavaScript program to the retrieved data, like this:

const testJSON = {
  "library": [
    {
      "title": "The Great Journey",
      "author": "F. Scott Fitzgerald",
      "yearPublished": 1925,
      "genre": "Adventure"
    },
    {
      "title": "A Quiet Place",
      "author": "Harper Lee",
      "yearPublished": 1960,
      "genre": "Fiction"
    },
    {
      "title": "Bright Future",
      "author": "George Orwell",
      "yearPublished": 1949,
      "genre": "Philosophical"
    }
  ]
};

const specificBook = testJSON.library.find(book => book.title === "Bright Future" && book.author === "George Orwell");

console.log(specificBook); // Output the log

/*
Found data.

{
  author: "George Orwell",
  genre: "Philosophical",
  title: "Bright Future",
  yearPublished: 1949
}
*/

However, this method may lead to a decrease in performance proportional to the amount of data.

@onemoretime, Thank you for the example of JSON. The code is clear and may be a way out of my dilemma. However, I do not want my data affected by slow performance. It will frustrate people and discourage them from using my website.

I hope that Wix provides a solution.

Thanks again for your help.

I see… :smiling_face_with_tear: The reason I mentioned the potential for performance degradation is that I generally believe that in cases of text matching searches, performance correlates with data volume. However, I also think that even if there is an impact on performance with tens of thousands of records, it may still be relatively minor.

Additionally, when considering searches by name, I believe that if the data is organized beforehand and divided into separate collections, it could improve search speed. For example, if I sort the collections alphabetically, one collection could contain names starting with A to C, while another could hold those from D to F, and so on.

So, if I want to search for someone whose name starts with Z, it makes sense that searching from the beginning of the list starting with A would take time. However, if I search from the end of the list, I could find it almost immediately.

It’s unfortunate that you’ve decided to abandon this approach this time, but if you have the opportunity to try this method in the future, please consider organizing the data first and give it another shot! :wink: :raised_hands:

Linking an update shared in another topic:

Closing the replies here to make it easier for everyone to follow the conversation :slight_smile: