I want to build a similar post recommendation system that a user sees after performing some activity on the news feed. For example: If he/she spends more time on sports posts, giving him/her sports recommended post so I would like to get help on what kind of dataset do I need to build a post recommendation system that a user likes to see. I am confused on should I build a dataset of my own if yes how can I build these recommendation posts? Thank you in advance!!
Hello and welcome to the forum! I recommend against building a dataset of your own as real world datasets have certain properties (distribution, missing data, noise) which are quite hard to replicate artificially.
You included Kaggle in your tags. Why don't you use it? It looks perfect for the job. Here's a list of options with the #recommender-systems tag.
This one and this one are about films. This other one is about user interactions with a news platform.
If this answered your question, please don't forget to accept it by clicking on the Tick button at the left of the answer. Have fun!
I'm trying to search some guidelines to create my first app for a price list. If I search on Google I find only ready system but I'd like to make something customized. My needs are to import a 3-4000 lines excel sheet for products with different measures and give to customers the possibility to make a quotation with their personal discount and place an order our make only a quotation for logged users. Instead for not logged user to see only product without prices. Then I don't know if it's better to make contents downloadable or to load all contents inside the app. I think it's better to download contents, so I can update prices directly without make them download each time an app update. Then a possibility to show some pop-up with products news, sometimes in a month. I'm yet practice with magento, WordPress and sql queries. I think The best for me is to find some kind of cms, for phone app, if they exist. Cross platform maybe the best. To understand something like wish or geek. I wait for your replies. Thank you guys!
I have a CakePHP website used by multiple clients. Each client shall be able to see slightly different input fields in forms. This is due to client preferences.
A simplified example:
Clients should be able to look up books from a big list. While some clients prefer to look up by author, others might want to look up by publish date or title. But each client should only see one input field in his search page. I don't want to bother the client with too many choices.
While creating different themes and switching them for each client is an option, it quickly becomes a lot of work if we are talking about many views and many input fields. Same for placing lots of if/else in the view files.
The Controller logic could be shared for all clients, as an empty or not existing input field will be ignored by my controller when looking up books.
Optimal I have some kind of dynamic configuration which states for each client which input field to show or hide on which page.
Let me know any suggestions on this or what is a good CakePHP way to achieve this.
If I get this right just use an element per client:
echo $this->element('client_forms/' . $clientIdentifier);
I need to develop a web chat with one "advanced" feature: grouping chat - like the Skype's chatting system.
The theory is trivial, but in practice it is very hard. Since last friday I was thinking about this, but I have no idea of how I can apply this architecture. Basically I need a database's design with a good structure without store redundancy.
Ok....... so far it seems simple, but now I'll introduce our main feature: history by user.
I can create one chat with 2 users. Ok, two days passed and I want to add a third user to join the conversation. The chat's history for him will be different: he will not be able to view old messages in that chat.
Wonderful, huh? Remember, friends: I can not use XML to store the history locally. I NEED to user a SQL Database. In my case, I'm using SQL-Server, from Microsoft.
Can you all understand my problem? If yes, isn't trivial, huh? Ok. Can someone think how I can solve this problem? I'm going crazy!
Actually the problem is trivial. Storing it in XML would be the real problem.
Users (UserId, Name)
Chat (ChatId, ChatName)
ChatParticipation (ChatParticipationId, UserId, JoinChatMessageId, LeaveMessageId)
ChatMessages (ChatMessageId, ChatId, UserId, Message)
By adding the ChatParticipation table you will know exactly which is the ChatMessageId at which the user joined the chat (JoinChatMessageId) and don't show him messages prior messages. LeaveMessageId can track when he left the chat room. Multiple join/leaves can be modeled as separate participation.
You haven't said what language (PHP etc).. So it's kinda hard, but, if I was creating this from a PHP point of view I would have the chat based upon id's. www.site.com/chat.php?id={id} and then have a way to accept / decline the user accordingly.
I can create one chat with 2 users. Ok, two days passed and I want to add a third user to join the conversation. The chat's history for him will be different: he will not be able to view old messages in that chat.
Why not give each message a date and a time, and then when a user member enters the chat, they can only see the messages from this date/time? This could work in theory.
So if I joined the chat today at 15:20pm then I can only see messages on or after 15:21.
Your main problem is going to displaying the messages in real-time, because it is a web application..
Good luck!
I am not sure, whether I understand your problem correctly.
As far as I understand it, you need 4 tables:
user (userid, username),
conversation (conversationid, conversationtitle),
user_conversation (userid, conversationid)
post (userid, conversationid, text)
user stores all users registered in your system. conversation stores all conversations. user_conversation maps theusers to the conversations they are allowed into. Post stores the posts a user has made in a certain conversation.
Now you can simply retrieve data from post by user, by conversation or both. If you dont want a user to see older posts, add a date field.
Regards
Luigi
i need a module that is kind of a cross between a registration module and a form module.
it need to allow for custom form fields to be saved to the DB and work as part of a flow such that once data is entered by the users they click next and see the data to confirm it is correct. at this point they should have the option to edit the data if they notice an error or continue to a payment page.
the payment page needs to have a module that can integrat with payment gateways liek paypal and accept credit cards. once credit card data is entered and the transaction is complete a custom email with a unique userNumber needs to be sent to the user.
i figure im lookign at three separate modules for this typeof work flow. but i hope since this is a standard type of register, pay, email confirm operation there may be a single module i can confugure to meet my needs.
thoughts? suggestions?
Have you looked at DNM RAD by DotNet Mushroom?
http://www.dotnetmushroom.com/DNMRADGeneral/GeneralInformation/WhatisDNMRAD/tabid/2347/Default.aspx
I have not had a use for this yet, but it is a module that I have on my short list in case the need comes up. They do state that they can work with pament gateways.
Good luck.
You might have to be somewhat flexible with your work flow if you want to used 100% canned modules.
FormMaster is a pretty good form solution. You can write to existing database tables, structure SQL tables or just the default is an XML file. It doesn't go through a preview before saving though.
FormMaster Website
Searching snowcovered.com you can certainly find something that can process a payment. That one shouldn't be too difficult.
I'm thinking you may need to sling some code to get the exact experience you are looking for.