知识库网络应用程序——需要演示模式
我受雇建立一个在线知识库，为某个利基行业搜索和交叉引用数千个替换零件。我的客户以订阅方式向他的客户提供此应用程序。
它使用 MySQL 和 PHP，并且运行良好。我想以“演示模式”部署它来推销我的技能。我希望用户看到这些功能，但我必须为我的客户保护数据。
我的第一个想法是混淆结果。这与显示其搜索效果是矛盾的。我正在考虑限制您可以执行的搜索次数，但这也很尴尬，因为有人可以每天访问并获得比我们希望的更多答案。
我发现的其他帖子是关于让人们与应用程序交互，但没有保护大型知识库的挑战。
你能建议一种方法吗？ （注意，我放置了标签混淆，但不确定它是否适用，因为java代码混淆似乎不相关。）
更新1：关于混淆......我有点想要（或假设，或幻想）即时混淆。我认为这本身就很难。到目前为止，一个答案意味着一次性的争夺，如果我这样做的话，这可能就是我需要解决的方法。
更新 2：感谢您对合法使用的两个警告。这一切都在向上！我和白天一样有道德，但也几乎一样无知。
更新 3：我有两个回复，质量都很好。 Chris L. 让我“跳出框框思考”，并提供了似乎是最好的解决方案。
最后：...而且没有那么多可以展示！
I was contracted to build an on-line knowledge base that searches and cross-references many thousands of replacement parts for a niche industry. My client furnishes this app to his customers on a subscription basis.
It uses MySQL and PHP and it works great. I want to deploy it in "demo mode" to sell my skills. I want the user to see the functions, but I have to guard the data for my client.
My first idea was to obfuscate the results. That's at cross-purposes with showing how well it searches. I'm considering a limit on how many searches you can perform, but that's awkward too as someone could visit every day and get more answers than we would prefer.
Other posts I've found are about letting people interact with an app, but without the challenge of protecting a big knowledge base.
Can you suggest an approach? (Note, I put the tag obfuscation, but not sure it applies because java code obfuscation seems to be unrelated.)
UPDATE 1: About obfuscation ... I've kind of wanted (or assumed, or fantasized about) on-the-fly obfuscation. Which is kind of hard in itself, I think. One answer so far implies a one-time scramble, which is probably how I need to approach this if I do it.
UPDATE 2: Thanks for the two warnings on legitimate use. This is all on the up-and-up! I'm as ethical as the day as long, and almost as ignorant.
UPDATE 3: I have two responses, both excellent quality. Chris L. got me to "think outside the box" and provided what seems to be the best solution.
FINAL: ... and there's not that much to show anyway!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
屏幕截图（或类似的东西）是你最好的选择。它们速度快、易于浏览，而且没有人在查看它们时真正思考它们在做什么。
确保您已获得客户的批准。
Screen shots ( or something similar) are your best bet. They are quick, easy to browse, and no one has to really think about what they are doing as they are looking at them.
Make sure you have approval from your client.
从法律上讲，要非常小心：复制此类系统（尤其是其数据）并将其用于您自己的目的可能会让您陷入很多困境水取决于您签署的合同以及（根据美国法律）该系统是否被视为雇佣工作。
也就是说，我个人对这样的系统的偏好是数据混淆。更改与搜索的不同部分相关的名称和编号，以创建一个展示相同功能但针对不同的、完全虚构的行业的系统。 （将东西变成小部件、小工具、小工具等等。）
如果潜在客户表现出足够的兴趣，看看您是否可以与原始客户安排一个限时演示帐户，以演示系统的全部功能。
Legally speaking, be very careful: taking a copy of a system of this sort (especially its data) and using it for your own purposes can get you into a lot of hot water depending on the contracts you signed and (under US law) whether or not the system was considered a work-for-hire.
That said, my personal preference for a system like this would be data obfuscation. Change the names and numbers associated with the different parts for which it searches in order to create a system which demonstrates equivalent functionality but for a different, wholly fictional industry. (Turn things into widgets, gadgets, whatzits and so forth.)
If a potential client shows sufficient interest, see if you can arrange for a limited-time demo account with your original client to demonstrate the system at full functionality.
假设您拥有应用程序本身，问题就在于数据。 “我不是律师”，但无论我如何混淆，我都不会使用客户的数据。从头开始生成数据集。
许多年前，我在一家公司工作，我们获取了客户的数据集，对其进行了清理，更改了名称以保护无辜者等等，并将其用于屏幕截图。你可能会认为它自己的母亲不可能认出它。错误的。一段时间后，其数据的客户对我们说“那是我们的数据”。没有人被起诉，甚至没有任何怨恨，但事实是，无论你对它做什么，它仍然不是你的数据。
“我和今天一样有道德，但几乎一样无知。”如果搞砸了，你的好意可能就毫无意义了。
祝你好运。
Assuming you own the application itself, the issue is that data. "I am not a lawyer", but I would not use a clients data no matter how I obfuscated it. Generate data set from scratch.
Many years ago I was with a company and we took a client's data set, cleaned it up changed the names to protect the innocent, etc etc etc, and used it for screen shots. You would have thought its own mother couldn't have recognized it. Wrong. Some time later, the client whose data it was said to us "That's our data." Nobody got sued, and there were not even any hard feelings, but the fact is, no matter what you do to it it is still not YOUR data.
"I'm as ethical as the day as long, and almost as ignorant." Your good intentions may count for nothing if you screw up.
Good luck.
如果我处于您的位置，我只会创建一些示例数据来填充数据库和所有其他最终使用的内容。
然后，我会选择以下一个或多个选项来向客户展示产品：
屏幕投射通常比屏幕截图更有效（给客户带来令人惊叹的效果） ，但创建它们有点棘手。尽管如此，Screenflow (Mac) 等软件仍然可以让他们的创作变得简单快捷。
我个人会避免数据混淆。在过去，有时很难向客户解释数据仅出于演示目的而被混淆（即使明确说明了这一点）。我从客户那里得到的反应仍然很困惑。
If I were in your shoes, I would simply create some sample data to populate the database and every other eventual content used.
Then, I would choose one or more of the following options to present the product to the client:
Screen casts are usually more effective than screen shots (the wow effect on the client), but they are a bit more tricky to create. Still, softwares such as Screenflow (Mac) make their creation easy and quick.
I would personally avoid data obfuscation. In the past, it turned out to be very difficult sometimes to explain the customer the data were obfuscated for the demo purposes only (even if this was explicitly stated). The reaction I got from the client was still of great perplexity.