4 ms·
Great job on the site, it looks very well done. As for your feedback goes, I'm concerned that you've spent 10 months on a project but don't seem to know the ma
by brd 13y ago
Great job on the site, it looks very well done.
As for your feedback goes, I'm concerned that you've spent 10 months on a project but don't seem to know the market at all. Have you talked to any schools about it? What made you start the project? Do you have prior experience working with ACMS?
I think your first goal should be to understand the administrative side of catalog management. How do they store/manage catalog information? Is this going to be easier to maintain than their current system? Can you make it easy to port from old systems? How do their systems connect with Bursar office, etc?
I think the biggest problem you will have is that catalog systems are probably integrated into larger ERP systems. Unless you can solve the integration problem you are probably going to have a very hard time selling this.
- vital101 13y agoI have talked with a few people that work in campus IT about their catalog management systems. The general feeling is that they wish there was something better out there. I have a little experience with ACMS from the admin side, but most of my experience comes from the student-facing side, which is generally pretty awful. I completely agree that I need to understand the administrative side of this better. My only problem is that I can't get access to existing systems. I'll probably need to find people who deal with this on a daily basis to get that information. I do plan on having a nice REST API for importing from old systems. I also intend to write middleware for importing from the current big players. I was inspired to add that to my to-do list by how easy BitBucket made it to transfer all of my private repos over from GitHub. Good point about existing ERP systems. I'll have to look into how integration with the big players(SAP, etc) in that arena works. Thanks for the feedback!