The core project team has met to revise the Strengths and the Weaknesses attributes of our project as well as the Opportunities and the Threats conditions that could impact the project performance.
Our strengths are basically the knowledge we have of the ticTOCs service; our expertise on RSS metadata schemas; the experience of our team members that have worked in related projects; our links with our community of users; and that the fact that our planned budget give us a lot of options for organising the best possible community engagement activities.
On the other hand, we have found that we were lacking of expertise in implementing RESTful principles to code APIs; we have to deal with time constraints as our project members are part of different short projects, competing for our attention. One additional weaknesses is the assumption that we have made regarding the metadata for solving the second use case (“Alerting when deposited papers have been published”) has shown to be not exact and may not work for all our users.
Some unforeseen opportunities have arisen that have started to have a positive effect on our project. For example, our developer, who is also working for the BayesianFF project, has had the opportunity to have access to an experimented developer expertise; from the beginning of the project, work is being done in consultation with the IR managers’ community through the UKCoRR channel and support (so far we have identified more than 15 “active” users); A major publisher has offered us to work with their Open Repository product and user community; additionally the communication with our sister projects such as Bibliosight has been very positive; the possibility that the outcomes of the project will be integrated and maintained by the techXtra service.
Some threats have also been identified, such as the time frame for testing the API would be too short (we are already in the middle of the planned project duration); the poor quality of the RSS metadata may produce poor results that consequently may decrease user enthusiasm (Users want a complete solution whereas we can only offer a partial solution at best. Even if we can get the affiliation info for all our feeds, there are still many journals that don’t have feeds); competing commercial alternatives, such as the Web of Science product may have a negative impact in the user’s interest. Finally the fact that we will not prototype additional specific protocols, products or data schemas (such as CRIS) may reduce user-interest for our tools.
We are taking note of these points in order to find ways to use and capitalize on our strength, improve our weak points, make use and benefit from our opportunities and alleviate each threat!