<!-- Google Analytics recording --> <bean class="org.dspace.google.GoogleRecorderEventListener"> <property name="eventService" > <ref bean="dspace.eventService"/> </property> </bean>
<property name="sidebarFacets"> <list> <ref bean="searchFilterAuthor" /> <ref bean="searchFilterSubject" /> <ref bean="searchFilterIssued" /> <ref bean="searchFilterSpeciality" /> </list> </property> <!-- Set TagCloud configuration per discovery configuration --> <property name="tagCloudFacetConfiguration" ref="defaultTagCloudFacetConfiguration"/> <!--The search filters which can be used on the discovery search page--> <property name="searchFilters"> <list> <ref bean="searchFilterTitle" /> <ref bean="searchFilterAuthor" /> <ref bean="searchFilterSubject" /> <ref bean="searchFilterIssued" /> <ref bean="searchFilterSpeciality" /> </list> </property>
<property name="sidebarFacets"> <list> <ref bean="searchFilterAuthor" /> <ref bean="searchFilterSubject" /> <ref bean="searchFilterIssued" /> <!-- <ref bean="searchFilterSpeciality" /> --> </list> </property> <!-- Set TagCloud configuration per discovery configuration --> <property name="tagCloudFacetConfiguration" ref="homepageTagCloudFacetConfiguration"/> <!--The search filters which can be used on the discovery search page (same as defaultConfiguration above)--> <property name="searchFilters"> <list> <ref bean="searchFilterTitle" /> <ref bean="searchFilterAuthor" /> <ref bean="searchFilterSubject" /> <ref bean="searchFilterIssued" /> <!-- <ref bean="searchFilterSpeciality" /> --> </list> </property>
<bean id="searchFilterSpeciality" class="org.dspace.discovery.configuration.HierarchicalSidebarFacetConfiguration"> <property name="indexFieldName" value="speciality"/> <property name="metadataFields"> <list> <value>local.thesis.specialitycode</value> </list> </property> <property name="facetLimit" value="10"/> <property name="sortOrder" value="COUNT"/> <property name="splitter" value="::"/> </bean>
webui.itemdisplay.default= .............. dc.identifier.rsi(rsi), dc.identifier.scopus(scopus), dc.identifier.wos(wos), dc.identifier.doi(doi), dc.description.sponsorship, local.fund.rsf(rsf), local.fund.nsf(nsf), local.fund.cordis(cordis) .................... webui.resolver.1.urn = doi webui.resolver.1.baseurl = [dx.doi.org] webui.resolver.2.urn = pure webui.resolver.2.baseurl = [science.urfu.ru] webui.resolver.3.urn = scopus webui.resolver.3.baseurl = [www.scopus.com]- webui.resolver.4.urn = rsi webui.resolver.4.baseurl = [elibrary.ru] webui.resolver.5.urn = wos webui.resolver.5.baseurl = [gateway.webofknowledge.com] webui.resolver.6.urn = rsf webui.resolver.6.baseurl = [grant.rscf.ru]? webui.resolver.7.urn = nsf webui.resolver.7.baseurl = [www.nsf.gov] webui.resolver.8.urn = cordis webui.resolver.8.baseurl = [cordis.europa.eu]Точечками удалил оверквотинг. Работает только в JSPUI, для XMLUI нужно будет вносить правки на уровне шаблона/темы.
<a class="statisticsLink btn btn-primary" href="http://scholar.google.ru/scholar?q=http://elar.urfu.ru<%= locationLink %>" target="_blank" alt="Scholar">Google Scholar</a>
10.0.3.214 - - [28/Mar/2020:22:16:14 +0500] "GET /handle/123456789/173414 HTTP/1.1" 200 18136 10.0.3.214 - - [28/Mar/2020:22:16:16 +0500] "GET /tools/edit-item?item_id=163848&submit=%D0%A0%D0%B5%D0%B4%D0%B0%D0%BA%D1%82%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D1%82%D1%8C... HTTP/1.1" 200 75839Т.е. зная handle и/или id можно примерно понять время.
2020-03-28 22:16:11,574 INFO org.dspace.usage.LoggerUsageEventListener @ admin@local:session_id=ADB75C696DC56E544E1AFE9F13633CCE:ip_addr=10.0.3.214:view_collection:collection_id=1672 2020-03-28 22:16:14,371 INFO org.dspace.app.webui.servlet.HandleServlet @ admin@local:session_id=ADB75C696DC56E544E1AFE9F13633CCE:ip_addr=10.0.3.214:view_item:handle=123456789/173414 2020-03-28 22:16:14,387 INFO org.dspace.usage.LoggerUsageEventListener @ admin@local:session_id=ADB75C696DC56E544E1AFE9F13633CCE:ip_addr=10.0.3.214:view_item:handle=123456789/173414 2020-03-28 22:16:20,543 INFO org.dspace.content.Collection @ admin@local:session_id=ADB75C696DC56E544E1AFE9F13633CCE:ip_addr=10.0.3.214:remove_item:collection_id=1672,item_id=163848 2020-03-28 22:16:20,543 INFO org.dspace.content.Item @ admin@local:session_id=ADB75C696DC56E544E1AFE9F13633CCE:ip_addr=10.0.3.214:delete_item:item_id=163848 2020-03-28 22:16:20,543 INFO org.dspace.content.Item @ admin@local:session_id=ADB75C696DC56E544E1AFE9F13633CCE:ip_addr=10.0.3.214:remove_bundle:item_id=163848,bundle_id=116543 2020-03-28 22:16:20,559 INFO org.dspace.content.Bundle @ admin@local:session_id=ADB75C696DC56E544E1AFE9F13633CCE:ip_addr=10.0.3.214:delete_bundle:bundle_id=116543 2020-03-28 22:16:20,559 INFO org.dspace.content.Bundle @ admin@local:session_id=ADB75C696DC56E544E1AFE9F13633CCE:ip_addr=10.0.3.214:remove_bitstream:bundle_id=116543,bitstream_id=127976 2020-03-28 22:16:20,559 INFO org.dspace.content.Bitstream @ admin@local:session_id=ADB75C696DC56E544E1AFE9F13633CCE:ip_addr=10.0.3.214:delete_bitstream:bitstream_id=127976 2020-03-28 22:16:20,559 INFO org.dspace.content.Bundle @ admin@local:session_id=ADB75C696DC56E544E1AFE9F13633CCE:ip_addr=10.0.3.214:remove_bitstream:bundle_id=116543,bitstream_id=127977 2020-03-28 22:16:20,559 INFO org.dspace.content.Bitstream @ admin@local:session_id=ADB75C696DC56E544E1AFE9F13633CCE:ip_addr=10.0.3.214:delete_bitstream:bitstream_id=127977 2020-03-28 22:16:20,621 WARN org.dspace.discovery.IndexEventConsumer @ REMOVE event, could not get object for BUNDLE id=116543, perhaps it has been deleted. 2020-03-28 22:16:20,621 WARN org.dspace.discovery.IndexEventConsumer @ MODIFY event, could not get object for ITEM id=163848, perhaps it has been deleted. 2020-03-28 22:16:20,621 WARN org.dspace.discovery.IndexEventConsumer @ REMOVE event, could not get object for ITEM id=163848, perhaps it has been deleted.В котором и IP и username уже четко есть. Правда, если перед томкэтом будет проксик, то не исключено что IP всегда будет один. На всякий случай, логин в данном примере - admin@local